Loading vulnerability…
CVE-2026-53166 is a Linux kernel denial-of-service vulnerability in futex priority-inheritance requeue handling. In the FUTEX_CMP_REQUEUE_PI path, when a non-top waiter is requeued onto a target PI futex that it already owns, task_blocks_on_rt_mutex() returns -EDEADLK before initializing waiter->task. The subsequent cleanup path calls remove_waiter() from rt_mutex_start_proxy_lock(), which dereferences waiter->task even though it is still NULL, causing a kernel NULL pointer dereference and crash. The issue was addressed by adding a self-deadlock check for non-top waiters before calling rt_mutex_start_proxy_lock(), analogous to the existing top-waiter check in futex_lock_pi_atomic().
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A separate null-pointer-dereference regression introduced by the initial patch for GhostLock, requiring a follow-up fix.
A separate Linux kernel crash bug introduced by the initial fix for GhostLock, relevant because some early patched builds may still be incomplete.
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.