CVE-2022-48786 is a Linux kernel AF_VSOCK lifecycle flaw in vsock_connect(). If a task waiting for a connection is interrupted by a pending signal after the socket has reached TCP_ESTABLISHED state, the socket can remain in the vsock connected-socket table while its state is reset. A subsequent successful connect() retry adds the same socket to the connected table again, corrupting the list. The fix removes the socket from the connected table when signal interruption occurs while waiting for the connection.
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.
Linux kernel vsock connection-state flaw when a connection attempt is interrupted by a signal.
Linux kernel vsock connection-state handling flaw when a connect operation is interrupted by a signal.
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.