Loading vulnerability…
CVE-2024-39500 is a race condition between sock_map_close and sk_psock_put in the Linux kernel's socket-map implementation. After the final sk_psock_put reduces the psock reference count to zero, sk_psock_get returns NULL. However, sk_psock_drop may not yet have completed callback restoration, leaving the socket's close callback pointing to sock_map_close. Concurrent socket-map deletion and socket creation, insertion, and closure can encounter this inconsistent state and trigger WARN_ON_ONCE.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A race condition in Linux kernel socket-map cleanup can leave sock_map_close installed while sk_psock_get returns NULL, triggering a kernel warning. The advisory rates the vulnerability Medium, with CVSS v3 score 4.7, indicating local access, high attack complexity, low privileges, and potential high availability impact without confidentiality or integrity impact. The fix changes psock pointer handling and callback-cleanup sequencing.
Race condition in Linux kernel BPF sock_map socket teardown.
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.