CVE-2024-26923 is a race condition in the Linux kernel AF_UNIX SOCK_STREAM garbage collector during concurrent connect() processing. When an embryo socket is enqueued while garbage collection scans a candidate listening socket, and its peer carries file descriptors through SCM_RIGHTS, consecutive scan_children() passes can observe different child sets. This can incorrectly increment an object's inflight reference count and leave a dangling pointer on gc_inflight_list, resulting in a use-after-free condition. The upstream fix synchronizes garbage collection with connect() by acquiring and releasing the state lock of each garbage-collection-candidate listening socket before scanning its children.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Race condition between Unix-domain socket garbage collection and connect operations.
Race condition between garbage collection and connect operations in Linux kernel AF_UNIX sockets.
Linux kernel AF_UNIX garbage-collector race-condition flaw.
Race condition between AF_UNIX garbage collection and connection 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.