Use-after-free in Linux kernel TLS async decrypt partial read handling
CVE-2024-26582 is a use-after-free vulnerability in the Linux kernel networking/TLS receive path. According to the provided fix description, in net/tls, tls_decrypt_sg does not take a reference on the pages associated with clear_skb. As a result, tls_decrypt_done can call put_page() and release those pages prematurely. If the skb is then processed further during a partial read, process_rx_list may subsequently access data from the partially-read skb after the backing pages have already been freed, resulting in a use-after-free condition. The bug is specifically associated with the interaction between partial reads and asynchronous decryption in the kernel TLS implementation.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability identified as CVE-2024-26582, referenced in the context of kernelCTF, mitigation material, writeups, and proof-of-concept updates.
A specific vulnerability identified as CVE-2024-26582 is referenced in a kernelCTF-related context, but no technical details or impact information are provided in the content.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.