Kernel crash via asynchronous TLS socket race
Published Feb 21, 2024 · Updated Aug 5, 2026
Use-after-free in affected Linux kernel TLS releases allows local users to crash the kernel by racing async crypto completion with socket close. The kTLS software paths in net/tls/tls_sw.c allow the recvmsg or sendmsg thread to exit after the asynchronous handler calls complete(), leaving later handler code to access freed request data. Reachability requires local socket operations using asynchronous kTLS crypto, and the documented consequence is a kernel panic rather than data disclosure or modification.
Summary
What happened
Use-after-free in affected Linux kernel TLS releases allows local users to crash the kernel by racing async crypto completion with socket close. The kTLS software paths in net/tls/tls_sw.c allow the recvmsg or sendmsg thread to exit after the asynchronous handler calls complete(), leaving later handler code to access freed request data. Reachability requires local socket operations using asynchronous kTLS crypto, and the documented consequence is a kernel panic rather than data disclosure or modification.
The record
- CVE
- CVE-2024-26583
- Published
- Feb 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0cada33241d9de205522e3858b18e506ca5cce2c <6209319b2efdd8524691187ee99c40637558fa33
- Affected versionversion=0cada33241d9de205522e3858b18e506ca5cce2c <7a3ca06d04d589deec81f56229a9a9d62352ce01
- Affected versionversion=0cada33241d9de205522e3858b18e506ca5cce2c <86dc27ee36f558fe223dbdfbfcb6856247356f4a
- Affected versionversion=0cada33241d9de205522e3858b18e506ca5cce2c <aec7961916f3f9e88766e2688992da6980f11b8d
- Affected versionversion=0cada33241d9de205522e3858b18e506ca5cce2c <f17d21ea73918ace8afb9c2d8e734dbf71c2c9d7
- Affected versionversion=5.4.44 <5.5
- Affected versionversion=5.6.16 <5.7
- Affected versionversion=5.7
- Affected versionversion=9b81d43da15e56ed89f083f326561acdcaf549ce
- Affected versionversion=cf4cc95a15f599560c7abd89095a7973a4b9cec3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo