CVE-2025-40248 is a race-condition vulnerability in the Linux kernel's vsock connect() handling, introduced in kernel version 3.9. Processing a signal or timeout can incorrectly disconnect a socket whose connection has already become established. Packet cancellation can race with sendmsg() credit accounting, permanently elevating vvs->bytes_unsent and disrupting SOCK_LINGER handling. Resetting socket state can also race with sockmap insertion, leaving a disconnected socket in the map and generating kernel warnings. Transitioning from SS_CONNECTED to SS_UNCONNECTED permits a transport change or removal after TCP_ESTABLISHED, potentially causing a use-after-free or null-pointer dereference during concurrent sendmsg() or connect() operations.
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.
38 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vsock race-condition vulnerability triggered when connect() handles a signal or timeout by disconnecting an already established socket. Concurrent operations can cause incorrect credit accounting, violate sockmap assumptions, or result in use-after-free and null-pointer dereference. The reference assigns a CVSS v3 base score of 7.8, with local access and low privileges required.
A Linux kernel vsock vulnerability that may cause memory corruption. Affected Rocky Linux 10.1 kernel packages have security updates under CIQ advisory crlsa-2026_1690.
A Linux kernel vsock race-condition vulnerability occurs when connect() handles a signal or timeout by disconnecting an already established socket. Concurrent socket operations can cause incorrect accounting, inconsistent sockmap state, and use-after-free or null-pointer dereference. The reference assigns a CVSS v3 score of 7.8, with local access and low privileges required. It recommends updating the linux package and related packages to version 6.1.159-1 or later.
A Linux kernel vsock race condition in connect() handling for already-established sockets. Signal or timeout processing could reset or disconnect an established socket, causing state and concurrency issues including potential use-after-free or null-pointer dereference. The affected Google COS kernel packages should be updated to version 18244.521.55 or later.
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.