Loading vulnerability…
CVE-2024-26583 is a race condition in the Linux kernel TLS implementation between asynchronous notification handling and socket closure. A thread that submitted a recvmsg or sendmsg operation can exit after an asynchronous cryptographic handler invokes completion, while code executing afterward can still access data already freed by the exiting thread. The fix holds an additional reference from the main thread and uses atomic reference counting to synchronize object lifetime.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel TLS race condition between asynchronous notification handling and socket closure that can result in use of already freed data. The referenced Google COS sys-kernel/lakitu-kernel-6_1 update resolves the flaw.
Linux kernel TLS race condition between asynchronous notification and socket closure.
Linux kernel TLS implementation race between asynchronous notification and socket closure.
Linux kernel TLS asynchronous-notification and socket-close race 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.