Loading vulnerability…
CVE-2026-52973 is a Linux kernel futex vulnerability caused by incorrect assumptions in the logic that decides when to allocate the private default futex hash. The affected code tied need_futex_hash_allocate_default() to strict pthread semantics by relying on CLONE_THREAD, but this was too narrow for cases where an address space is shared through other CLONE_VM-based cloning patterns. Under those conditions, the non-concurrency assumptions around per-CPU mm->futex_ref allocation can be violated, allowing stale references to persist after mm->futex_ref no longer points to the original per-CPU counter. This can result in a slab use-after-free in futex_hash_put. The upstream fix broadens the condition to cover CLONE_VM clones except vfork(), avoiding the invalid lifetime assumptions that led to the memory-safety flaw.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.