CVE-2026-97429

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-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 mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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

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

drm/amdkfd: fix UAF race in destroy_queue_cpsch

wait_on_destroy_queue() drops locks to wait for queue resume, allowing a concurrent destroy to free the queue. Use is_being_destroyed flag to serialize destruction.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

drm/amdkfd: fix UAF race in destroy_queue_cpsch - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdkfd: fix UAF race in destroy_queue_cpsch - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdkfd: fix UAF race in destroy_queue_cpsch - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41144829f4645c2bd4cb501d34d253858f750c0a

Vendor Advisories for CVE-2026-97429(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 41× in last 7d / 61× 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-10-05 02:06 UTCEG score recompute
  2. 2026-10-05 02:06 UTCVendor advisory
  3. 2026-10-05 02:06 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 13:13 UTCVendor advisory
  6. 2026-10-04 13:13 UTCGHSA enrichment
  7. 2026-10-04 00:22 UTCEG score recompute
  8. 2026-10-04 00:22 UTCVendor advisory
  9. 2026-10-04 00:22 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 11:31 UTCVendor advisory
  12. 2026-10-03 11:31 UTCGHSA enrichment
  13. 2026-10-03 01:45 UTCEG score recompute
  14. 2026-10-03 01:45 UTCVendor advisory
  15. 2026-10-03 01:45 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 12:54 UTCVendor advisory
  18. 2026-10-02 12:54 UTCGHSA enrichment
  19. 2026-10-02 00:03 UTCEG score recompute
  20. 2026-10-02 00:03 UTCVendor advisory
  21. 2026-10-02 00:03 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 10:50 UTCVendor advisory
  24. 2026-10-01 10:50 UTCGHSA enrichment
  25. 2026-09-30 21:59 UTCEG score recompute
Show 36 more
  1. 2026-09-30 21:59 UTCVendor advisory
  2. 2026-09-30 21:59 UTCGHSA enrichment
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-30 09:08 UTCVendor advisory
  5. 2026-09-30 09:08 UTCGHSA enrichment
  6. 2026-09-29 20:16 UTCEG score recompute
  7. 2026-09-29 20:16 UTCVendor advisory
  8. 2026-09-29 20:16 UTCGHSA enrichment
  9. 2026-09-29 07:23 UTCEG score recompute
  10. 2026-09-29 07:23 UTCVendor advisory
  11. 2026-09-29 07:23 UTCGHSA enrichment
  12. 2026-09-28 18:32 UTCEG score recompute
  13. 2026-09-28 18:32 UTCVendor advisory
  14. 2026-09-28 18:32 UTCGHSA enrichment
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 05:41 UTCGHSA enrichment
  18. 2026-09-27 16:50 UTCEG score recompute
  19. 2026-09-27 16:50 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 03:59 UTCEG score recompute
  22. 2026-09-27 03:59 UTCGHSA enrichment
  23. 2026-09-26 15:59 UTCEPSS rescore
  24. 2026-09-26 15:07 UTCGHSA enrichment
  25. 2026-09-26 02:16 UTCEG score recompute
  26. 2026-09-26 02:15 UTCGHSA enrichment
  27. 2026-09-25 13:21 UTCEG score recompute
  28. 2026-09-25 13:21 UTCGHSA enrichment
  29. 2026-09-25 12:55 UTCEG score recompute
  30. 2026-09-25 12:55 UTCGHSA enrichment
  31. 2026-09-25 05:17 UTCEG score recompute▲ 7.80
  32. 2026-09-25 05:17 UTCGHSA enrichment
  33. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  34. 2026-09-24 17:33 UTCNVD update
  35. 2026-09-24 16:29 UTCEG score recompute
  36. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97429?
CVE-2026-97429 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix UAF race in destroyqueuecpsch waitondestroy_queue() drops locks to wait for queue resume, allowing a concurrent destroy to free the queue. Use isbeingdestroyed flag to serialize destruction.
When was CVE-2026-97429 disclosed?
CVE-2026-97429 was first published on September 24, 2026, with the most recent update on October 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-97429 actively exploited?
CVE-2026-97429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97429?
CVE-2026-97429 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97429?
No fix for CVE-2026-97429 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97429 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97429

Explore →

Is Your Infrastructure Affected by CVE-2026-97429?

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

Book a Demo →Browse All CVEs