CVE-2024-53119 is a memory leak in the Linux kernel virtio-vsock transport's listener connection handling. During destruction of a listening vsock socket, its accept queue can be flushed before the asynchronous close work sets the SOCK_DONE state. A concurrently received connection request can pass the SOCK_DONE check and create and enqueue a new connected child socket after the queue has been flushed. That child is subsequently not removed, leaking its socket allocation. The fix prevents enqueueing accepted child sockets while socket shutdown is in progress by checking the socket shutdown state.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.