Skip to main content

Linux Kernel EUVDEUVD-2026-59229

| CVE-2026-72330 HIGH
2026-08-15 Linux GHSA-744x-88r4-xj59
7.5
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.9 MEDIUM

kTLS offloading requires explicit application-level configuration absent from default installs, elevating AC to H; no auth required from attacker; impact is availability-only per description.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 08:29 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.5 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 05:55 cve.org
HIGH 7.5
CVE Published
Aug 15, 2026 - 05:55 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

net/tls: Consume empty data records in tls_sw_read_sock()

A peer may send a zero-length TLS application_data record; TLS 1.3 explicitly permits these as a traffic-analysis countermeasure (RFC 8446, Section 5.1). After decryption such a record has full_len ==

  1. tls_sw_read_sock() hands it to the read_actor, which has no

payload to consume and returns zero. The loop treats a zero return as backpressure (used <= 0), requeues the skb at the head of rx_list, and stops. rx_list is serviced head-first on the next call, so the empty record is dequeued, fails the same way, and is requeued again; every later record on the connection is blocked behind it.

tls_sw_recvmsg() does not stall on this: a zero-length data record copies nothing and falls through to consume_skb(). Mirror that in the read_sock() path by recognizing an empty data record before the actor runs, consuming it, and continuing.

AnalysisAI

Denial of service in the Linux kernel's kernel TLS (kTLS) subsystem allows a remote peer to permanently stall a TLS connection by sending a single zero-length TLS 1.3 application_data record. The tls_sw_read_sock() function misinterprets the empty record's zero-length return as a backpressure signal, requeuing the record indefinitely at the head of rx_list and blocking all subsequent TLS data on that connection. No public exploit code exists, the CVE is absent from the CISA KEV catalog, and EPSS sits at 0.21% (11th percentile), indicating low current exploitation interest despite the 7.5 CVSS score.

Technical ContextAI

The vulnerability resides in the Linux kernel's net/tls subsystem (tls_sw.c), specifically the tls_sw_read_sock() receive path used by kernel TLS offloading (kTLS). TLS 1.3 (RFC 8446, Section 5.1) explicitly permits zero-length application_data records as a traffic-analysis countermeasure, so receiving them is standards-compliant behavior. When the kernel decrypts such a record, full_len equals zero; the read_actor callback has no payload to process and returns zero, which the receive loop incorrectly treats as a backpressure signal. The empty skb is re-enqueued at the head of rx_list on every iteration, creating a loop with an unreachable exit condition (CWE-835 class) that blocks every subsequent record queued behind it. The sibling path tls_sw_recvmsg() already handles this correctly by falling through to consume_skb() after copying nothing; the fix mirrors that behavior in tls_sw_read_sock(). Affected CPE: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* across multiple stable branches starting from commit 662fbcec32f4af6bdcf5b4006b792ebe9543d945.

RemediationAI

Upgrade to a fixed stable kernel release: 6.6.145 or later for the 6.6 LTS branch, 6.12.97 or later for the 6.12 branch, 6.18.40 or later for the 6.18 branch, or 7.1.5 or later for the 7.1 branch. The upstream fix commits are available at kernel.org: 0867b0f2513ebc1c475af9898c97f4772a68d964, c6b440cf766a557b08d25f1b571b3d57d039686e, e8a4c9fc437b16aef38f86ce3275677e36924259, ebc295ce343600c2d60c1e1e0c5d192080217457, and 3be28e2c9cd0230cb51fd4967df095273afd3848; distributions shipping backported stable kernels (RHEL, Ubuntu, SUSE, Debian) should be monitored for vendor-issued packages containing these commits. If immediate kernel upgrade is not feasible, disable kTLS offloading for all affected applications - in nginx this means removing or omitting the 'ssl_conf_command Options KTLS;' directive; the trade-off is reduced TLS throughput (kTLS offloads symmetric crypto to the NIC/kernel) in exchange for eliminating exposure. Systems not using kTLS are not affected and require no action.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

EUVD-2026-59229 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy