CVE-2026-80904

net/tls: Fail tls_sw_splice_read() after a failed async decrypt

N/A
Published: September 4, 2026 at 05:19 PM UTC
Updated: September 4, 2026 at 06:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net/tls: Fail tls_sw_splice_read() after a failed async decrypt When an async decrypt fails, tls_decrypt_done() records the error in ctx->async_wait.err and calls tls_err_abort(), which stores it in sk_err. tls_sw_recvmsg() and tls_sw_read_sock() each read async_wait.err once they hold the reader lock and fail the call: a record that did not authenticate breaks the connection. tls_sw_splice_read() has no such check, and sk_err does not stand in for one. tls_rx_rec_wait() tests sk_err only inside the loop it skips whenever a record is already parsed, and the first reader to reach sock_error() clears it, while async_wait.err persists. A splice therefore keeps delivering records on a connection that recvmsg() and read_sock() refuse to read. Read async_wait.err in tls_sw_splice_read() as the other two readers do.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.19 ≤ v < 6.1.1845.19 ≤ v < 6.12.1055.19 ≤ v < 6.18.465.19 ≤ v < 6.6.1535.19 ≤ v < 7.1.105.19 ≤ v < 7.25.19f314bfee81b1bf8e01168177b2f65f24eb8da63a
Vendor states this is fixed in 06c2a53604fa1dc4820063828d7dadb3675b7af8 (fixed)
Vendor states this is fixed in 18ae1e95f20867106a28820c208a9cec99dda861 (fixed)
Vendor states this is fixed in 4b177911eb9f799e9841c2f87c75b08cb112757a (fixed)
Vendor states this is fixed in 82d9269f01ebfd835b6256aa17016a974cbbc647 (fixed)
Vendor states this is fixed in 976df67f463db1fddaf2a32fb04f57ad2891a23d (fixed)
Vendor states this is fixed in a808aadff634c7a408b2ab84d5919e9a741fdb5b (fixed)
Vendor states this is fixed in 5.19 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card