Loading vulnerability…
CVE-2024-26582 is a use-after-free vulnerability in the Linux kernel TLS receive/decryption path. When processing a partially read socket buffer while asynchronous decryption is in use, tls_decrypt_sg() fails to acquire references for pages associated with clear_skb. tls_decrypt_done() can subsequently release those pages through put_page(), after which process_rx_list() may read the partially consumed socket buffer using freed memory.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel network TLS use-after-free vulnerability involving partial reads and asynchronous decryption.
A specific vulnerability identified as CVE-2024-26582, referenced in the context of kernelCTF, mitigation material, writeups, and proof-of-concept updates.
Linux kernel TLS implementation use-after-free during partial reads and asynchronous decryption.
Linux kernel TLS partial-read/asynchronous-decryption use-after-free vulnerability.
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.