net/tls: Fail tls_sw_splice_read() after a failed async decrypt (CVE-2026-80904) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80904

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

Answer in brief

CVE-2026-80904 records a Unknown severity vulnerability in net/tls: Fail tls_sw_splice_read() after a failed async decrypt. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 4, 2026Updated Sep 4, 2026Source checked Sep 4, 2026First seen by HOL Sep 4, 2026Material review Sep 4, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=f314bfee81b1bf8e01168177b2f65f24eb8da63a <a808aadff634c7a408b2ab84d5919e9a741fdb5b \|\| >=f314bfee81b1bf8e01168177b2f65f24eb8da63a <06c2a53604fa1dc4820063828d7dadb3675b7af8 \|\| >=f314bfee81b1bf8e01168177b2f65f24eb8da63a <18ae1e95f20867106a28820c208a9cec99dda861 \|\| >=f314bfee81b1bf8e01168177b2f65f24eb8da63a <82d9269f01ebfd835b6256aa17016a974cbbc647 \|\| >=f314bfee81b1bf8e01168177b2f65f24eb8da63a <4b177911eb9f799e9841c2f87c75b08cb112757a \|\| >=f314bfee81b1bf8e01168177b2f65f24eb8da63a <976df67f463db1fddaf2a32fb04f57ad2891a23d	a808aadff634c7a408b2ab84d5919e9a741fdb5b, 06c2a53604fa1dc4820063828d7dadb3675b7af8, 18ae1e95f20867106a28820c208a9cec99dda861, 82d9269f01ebfd835b6256aa17016a974cbbc647, 4b177911eb9f799e9841c2f87c75b08cb112757a, 976df67f463db1fddaf2a32fb04f57ad2891a23d
Linux/Linuxgeneric	5.19	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to a808aadff634c7a408b2ab84d5919e9a741fdb5b if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 4, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.