CVE-2026-80904 Affecting python3-perf package, versions <1:6.1.186-228.374.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-AMZN2023-PYTHON3PERF-19820628
- published15 Sept 2026
- disclosed4 Sept 2026
Introduced: 4 Sep 2026
NewCVE-2026-80904 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 python3-perf to version 1:6.1.186-228.374.amzn2023 or higher.
This issue was patched in ALAS2023-2026-2143.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python3-perf package and not the python3-perf package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
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.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-80904
- 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