CVE-2026-52973

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM 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 — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 24, 2026

Last Modified

September 3, 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(4)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
redhatkpatch-patch2026-09-02redhat
redhatkernel-0:5.14.0-687.31.1.el9_82026-07-28redhat
redhatkernel-0:6.12.0-211.39.1.el10_22026-07-24redhat

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.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 65× 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.

Showing the most recent 100 of 289 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 08:06 UTCEG score recompute
  3. 2026-09-18 08:06 UTCVendor advisory
  4. 2026-09-18 08:06 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 01:55 UTCEG score recompute
  8. 2026-09-14 01:55 UTCVendor advisory
  9. 2026-09-14 01:55 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 11:57 UTCVendor advisory
  12. 2026-09-13 11:57 UTCGHSA enrichment
  13. 2026-09-12 17:10 UTCEG score recompute
  14. 2026-09-12 17:10 UTCVendor advisory
  15. 2026-09-12 17:10 UTCGHSA enrichment
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-04 05:06 UTCEPSS rescore
  22. 2026-09-03 13:19 UTCEG score recompute
  23. 2026-09-03 13:19 UTCVendor advisory
  24. 2026-09-03 13:19 UTCGHSA enrichment
  25. 2026-09-03 12:26 UTCEG score recompute
Show 75 more
  1. 2026-09-03 12:26 UTCVendor advisory
  2. 2026-09-03 12:26 UTCGHSA enrichment
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-30 20:16 UTCEG score recompute
  7. 2026-08-30 20:16 UTCVendor advisory
  8. 2026-08-30 20:16 UTCGHSA enrichment
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-28 04:48 UTCEG score recompute
  13. 2026-08-28 04:48 UTCVendor advisory
  14. 2026-08-28 04:48 UTCGHSA enrichment
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 22:00 UTCEG score recompute
  19. 2026-08-24 22:00 UTCVendor advisory
  20. 2026-08-24 22:00 UTCGHSA enrichment
  21. 2026-08-24 04:38 UTCVendor advisory
  22. 2026-08-24 04:37 UTCGHSA enrichment
  23. 2026-08-23 13:49 UTCVendor advisory
  24. 2026-08-23 13:49 UTCGHSA enrichment
  25. 2026-08-23 01:31 UTCEG score recompute
  26. 2026-08-23 01:31 UTCVendor advisory
  27. 2026-08-23 01:31 UTCGHSA enrichment
  28. 2026-08-23 00:19 UTCEPSS rescore
  29. 2026-08-22 13:08 UTCEG score recompute
  30. 2026-08-22 13:08 UTCVendor advisory
  31. 2026-08-22 13:08 UTCGHSA enrichment
  32. 2026-08-21 23:49 UTCEPSS rescore
  33. 2026-08-21 20:25 UTCVendor advisory
  34. 2026-08-21 20:25 UTCGHSA enrichment
  35. 2026-08-21 08:07 UTCEG score recompute
  36. 2026-08-21 08:07 UTCVendor advisory
  37. 2026-08-21 08:07 UTCGHSA enrichment
  38. 2026-08-20 22:55 UTCEPSS rescore
  39. 2026-08-20 19:49 UTCVendor advisory
  40. 2026-08-20 19:49 UTCGHSA enrichment
  41. 2026-08-20 07:31 UTCEG score recompute
  42. 2026-08-20 07:31 UTCVendor advisory
  43. 2026-08-20 07:31 UTCGHSA enrichment
  44. 2026-08-19 17:04 UTCEPSS rescore
  45. 2026-08-19 14:52 UTCVendor advisory
  46. 2026-08-19 14:52 UTCGHSA enrichment
  47. 2026-08-19 02:14 UTCEG score recompute
  48. 2026-08-19 02:14 UTCVendor advisory
  49. 2026-08-19 02:14 UTCGHSA enrichment
  50. 2026-08-18 13:48 UTCEPSS rescore
  51. 2026-08-17 13:47 UTCEPSS rescore
  52. 2026-08-17 10:07 UTCVendor advisory
  53. 2026-08-17 10:07 UTCGHSA enrichment
  54. 2026-08-16 21:50 UTCEG score recompute
  55. 2026-08-16 21:50 UTCVendor advisory
  56. 2026-08-16 21:50 UTCGHSA enrichment
  57. 2026-08-16 14:56 UTCEPSS rescore
  58. 2026-08-16 09:32 UTCEG score recompute
  59. 2026-08-16 09:32 UTCVendor advisory
  60. 2026-08-16 09:32 UTCGHSA enrichment
  61. 2026-08-16 02:14 UTCEPSS rescore
  62. 2026-08-15 21:15 UTCVendor advisory
  63. 2026-08-15 21:15 UTCGHSA enrichment
  64. 2026-08-15 08:58 UTCEG score recompute
  65. 2026-08-15 08:58 UTCVendor advisory
  66. 2026-08-15 08:58 UTCGHSA enrichment
  67. 2026-08-15 01:30 UTCEPSS rescore
  68. 2026-08-14 20:41 UTCVendor advisory
  69. 2026-08-14 20:41 UTCGHSA enrichment
  70. 2026-08-14 08:24 UTCEG score recompute
  71. 2026-08-14 08:24 UTCVendor advisory
  72. 2026-08-14 08:24 UTCGHSA enrichment
  73. 2026-08-13 22:00 UTCEPSS rescore
  74. 2026-08-13 20:06 UTCVendor advisory
  75. 2026-08-13 20:06 UTCGHSA enrichment

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 September 3, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 95.3% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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