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…
Does this matter?
Not yet scored. NVD analysis is pending; check back once CVSS and EPSS values are published.
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.
- CVSS
- Not yet scored
- EPSS
- 0.16% probability · 6th percentile
- CISA KEV
- Not listed
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/06c2a53604fa1dc4820063828d7dadb3675b7af8
- https://git.kernel.org/stable/c/18ae1e95f20867106a28820c208a9cec99dda861
- https://git.kernel.org/stable/c/4b177911eb9f799e9841c2f87c75b08cb112757a
- https://git.kernel.org/stable/c/82d9269f01ebfd835b6256aa17016a974cbbc647
- https://git.kernel.org/stable/c/976df67f463db1fddaf2a32fb04f57ad2891a23d
- https://git.kernel.org/stable/c/a808aadff634c7a408b2ab84d5919e9a741fdb5b
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.