CVE Catalog

CVE-2026-80904

Low risk· EPSS 6%
Published: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.16%

6th percentile - higher than 6% of all known CVEs

Summary

In the Linux kernel net/tls subsystem, tls_sw_splice_read() does not check for errors after a failed async decrypt. Unlike other read functions, splice may continue delivering data on a connection that should be closed due to authentication failure.

Risk Assessment

This could lead to delivering unauthenticated data to applications, posing a data integrity security risk.

Recommendation

Install a Linux kernel update that includes the fix checking async_wait.err in tls_sw_splice_read().

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS