Loading vulnerability…
A data race vulnerability was identified in the Linux kernel's af_unix implementation, specifically involving the sk->sk_shutdown field. The write side (unix_release_sock) uses WRITE_ONCE to atomically update sk->sk_shutdown, but the read side (unix_stream_sendmsg) does not perform an atomic read, leading to a potential data race. This can result in inconsistent or unexpected behavior when sockets are being released and messages are being sent concurrently. The issue was not covered by previous fixes and specifically affects the unix_stream_sendmsg function, as other reads are protected by unix_state_lock.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Data-race flaws in Linux kernel Unix-domain socket release and stream-send paths.
Data-race vulnerability in Linux kernel AF_UNIX socket release and stream-send handling.
A Linux kernel AF_UNIX socket race-condition vulnerability in unix_release_sock and unix_stream_sendmsg.
Linux kernel AF_UNIX socket data-race flaw in socket release and stream send operations.
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.