CVE-2026-52973

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

futex: Drop CLONE_THREAD requirement for private default hash alloc

Currently need_futex_hash_allocate_default() depends on strict pthread semantics, abusing CLONE_THREAD. This breaks the non-concurrency assumptions when doing the mm->futex_ref pcpu allocations, leading to bugs[0] when sharing the mm in other ways; ie:

BUG: KASAN: slab-use-after-free in futex_hash_put

... where the +1 bias can end up on a percpu counter that mm->futex_ref no longer points at.

Loosen the check to cover any CLONE_VM clone, except vfork(). Excluding vfork keeps the existing paths untouched (no overhead), and we can't race in the first place: either the parent is suspended and the child runs alone, or mm->futex_ref is already allocated from an earlier CLONE_VM.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
2.8%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

futex: Drop CLONE_THREAD requirement for private default hash alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ee9dce44362b2d8132c32964656ab6dff7dfbc6a
generic

futex: Drop CLONE_THREAD requirement for private default hash alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/974ac49a9a068b0591a59f65c63eb06579a13091
generic

futex: Drop CLONE_THREAD requirement for private default hash alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1dcd36420af2da5bd59306dba9caf78e3d248b1d

Vendor Advisories for CVE-2026-52973(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 34× 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-07 04:00 UTCEG score recompute
  2. 2026-07-07 04:00 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:29 UTCEG score recompute
  6. 2026-07-06 15:28 UTCGHSA enrichment
  7. 2026-07-06 03:04 UTCEG score recompute
  8. 2026-07-06 03:04 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 14:45 UTCEG score recompute
  12. 2026-07-05 14:45 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 02:22 UTCEG score recompute
  16. 2026-07-05 02:21 UTCGHSA enrichment
  17. 2026-07-04 14:04 UTCEG score recompute
  18. 2026-07-04 14:04 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 01:46 UTCEG score recompute
  21. 2026-07-04 01:46 UTCGHSA enrichment
  22. 2026-07-03 13:28 UTCEG score recompute
  23. 2026-07-03 13:28 UTCGHSA enrichment
  24. 2026-07-03 01:11 UTCEG score recompute
  25. 2026-07-03 01:10 UTCGHSA enrichment
Show 21 more
  1. 2026-07-02 12:53 UTCEG score recompute
  2. 2026-07-02 12:53 UTCGHSA enrichment
  3. 2026-07-02 00:36 UTCEG score recompute
  4. 2026-07-02 00:36 UTCGHSA enrichment
  5. 2026-07-01 12:17 UTCEG score recompute
  6. 2026-07-01 12:17 UTCGHSA enrichment
  7. 2026-06-30 23:55 UTCEG score recompute▲ 7.80
  8. 2026-06-30 23:55 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 21:11 UTCEG score recompute
  17. 2026-06-27 21:11 UTCGHSA enrichment
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-24 18:27 UTCEG score recompute
  21. 2026-06-24 18:02 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52973?
CVE-2026-52973 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: futex: Drop CLONE_THREAD requirement for private default hash alloc Currently needfutexhashallocatedefault() depends on strict pthread semantics, abusing CLONE_THREAD. This breaks the non-concurrency assumptions when doing the…
When was CVE-2026-52973 disclosed?
CVE-2026-52973 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52973 actively exploited?
CVE-2026-52973 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52973?
CVE-2026-52973 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52973?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52973, 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-52973

Explore →

Is Your Infrastructure Affected by CVE-2026-52973?

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

Start Free Scan →Browse All CVEs