Loading vulnerability…
CVE-2026-53166 has been rejected or withdrawn by its CVE Numbering Authority; the reason for rejection is unspecified. The identifier was associated with a Linux kernel NULL pointer dereference in priority-inheritance futex requeue handling. When FUTEX_CMP_REQUEUE_PI requeues a non-top waiter that already owns the target PI futex, task_blocks_on_rt_mutex() returns -EDEADLK before initializing waiter->task. A subsequent remove_waiter() call in rt_mutex_start_proxy_lock() dereferences the NULL pointer, causing a kernel crash. The corrective change adds a self-deadlock check for non-top waiters before invoking rt_mutex_start_proxy_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.
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel futex/requeue vulnerability that can cause a NULL pointer dereference in remove_waiter() on self-deadlock.
A Linux kernel futex/requeue vulnerability that could cause a NULL pointer dereference in remove_waiter() on self-deadlock.
A Linux kernel futex/requeue NULL pointer dereference vulnerability in remove_waiter() triggered on self-deadlock.
A Linux kernel futex/requeue vulnerability involving a NULL pointer dereference in remove_waiter() on self-deadlock, fixed in this Red Hat advisory.
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.