CVE-2026-53166

✕ Withdrawn — historical dataMEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — Patch released this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock

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 setting waiter->task.

The subsequent remove_waiter() in rt_mutex_start_proxy_lock() dereferences the NULL waiter->task, causing a kernel crash.

Add a self-deadlock check for non-top waiters before calling rt_mutex_start_proxy_lock(), analogous to the top-waiter check in futex_lock_pi_atomic().

CVSS v3
5.5
EG Score
5.5(high)
EPSS
2.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
No patch confirmed yet.
generic

futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74e144274af39935b0f410c0ee4d2b91c3730414
generic

futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f2f3f3eacd6653ab215c5d2ea70811148d433fc
generic

futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16f8e17184b31382076f84751db5ac51fc02733e

Vendor Advisories for CVE-2026-53166(17)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-477.152.1.el8_82026-07-16redhat
redhatkernel-0:5.14.0-570.128.1.el9_62026-07-16redhat
redhatkernel-0:4.18.0-372.201.1.el8_62026-07-15redhat
redhatkernel-0:5.14.0-284.181.1.el9_22026-07-15redhat
redhatkernel-rt-0:5.14.0-284.181.1.rt14.466.el9_22026-07-15redhat
redhatkernel-0:4.18.0-305.198.1.el8_42026-07-15redhat
redhatkernel-rt-0:4.18.0-553.143.1.rt7.484.el8_102026-07-14redhat
redhatkernel-0:4.18.0-553.143.1.el8_102026-07-14redhat
redhatkernel-0:5.14.0-687.25.1.el9_82026-07-13redhat
redhatkernel-0:6.12.0-211.33.1.el10_22026-07-13redhat
redhatkernel-0:6.12.0-231.16.el10nv2026-07-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:39 UTCVendor advisory
  2. 2026-07-16 17:39 UTCGHSA enrichment
  3. 2026-07-15 17:44 UTCVendor advisory
  4. 2026-07-15 17:43 UTCGHSA enrichment
  5. 2026-07-14 18:55 UTCVendor advisory
  6. 2026-07-14 18:55 UTCGHSA enrichment
  7. 2026-07-13 20:04 UTCVendor advisory
  8. 2026-07-13 20:04 UTCGHSA enrichment
  9. 2026-07-12 21:18 UTCVendor advisory
  10. 2026-07-12 21:18 UTCGHSA enrichment
  11. 2026-07-11 22:11 UTCVendor advisory
  12. 2026-07-11 22:11 UTCGHSA enrichment
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-10 23:24 UTCGHSA enrichment
  16. 2026-07-10 00:37 UTCGHSA enrichment
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 01:44 UTCEG score recompute▲ 5.50
  20. 2026-07-09 01:43 UTCGHSA enrichment
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-07 18:13 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-07 13:46 UTCEPSS rescore
Show 21 more
  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 08:03 UTCGHSA enrichment
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 02:31 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 14:31 UTCGHSA enrichment
  11. 2026-07-01 15:07 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 21:04 UTCGHSA enrichment
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 03:36 UTCGHSA enrichment
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 10:09 UTCEG score recompute
  21. 2026-06-25 10:09 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53166?
CVE-2026-53166 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock When FUTEXCMPREQUEUE_PI requeues a non-top waiter that already owns the target PI futex, taskblocksonrtmutex() returns -EDEADLK before setting…
When was CVE-2026-53166 disclosed?
CVE-2026-53166 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53166 actively exploited?
CVE-2026-53166 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53166?
CVE-2026-53166 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53166?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53166, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53166

Explore →

Is Your Infrastructure Affected by CVE-2026-53166?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs