CVE-2026-80904
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 versions
Linux kernel versions
5.19
and later are affected. Fixed in
6.1.184,
6.6.153,
6.12.105,
6.18.46,
7.1.10,
7.2
and their respective stable series.
References
6 totalFrequently asked questions
-
What is CVE-2026-80904?
CVE-2026-80904 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.19 onward and has been patched in 6.1.184, 6.6.153, 6.12.105 and others. CVE-2026-80904 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-80904?
Yes. CVE-2026-80904 has been patched. Fixed versions include 6.1.184, 6.6.153, 6.12.105 and others. If you are running Linux kernel 5.19 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-80904 actively exploited?
No. CVE-2026-80904 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.