CVE-2026-97496

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
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.1Exploit: 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 OOB memory exposure in get_wave_state()

The get_wave_state() function for v9 trusts cp_hqd_cntl_stack_size and cp_hqd_cntl_stack_offset values read directly from the MQD, which are written by GPU microcode and fully attacker-controlled on the CRIU-restore path (via AMDKFD_IOC_RESTORE_PROCESS with H3).

this leads to an unbounded copy_to_user() that can leak adjacent GTT/kernel memory. If offset > size, integer underflow produces a ~4 GiB read length, if size is set to 1 MiB against a 4 KiB allocation, we leak 1 MiB of adjacent kernel memory (other queues' MQDs, ring buffers, KASLR pointers).

Fix by clamping both cp_hqd_cntl_stack_size to the actual allocated buffer size (q->ctl_stack_size) and cp_hqd_cntl_stack_offset to the clamped size before performing arithmetic and copy_to_user().

This ensures we never read beyond the allocated kernel BO regardless of attacker-supplied MQD field values.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
37
EG Risk 37/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
Severity71% × 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
1st
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 OOB memory exposure in get_wave_state() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdkfd: Fix OOB memory exposure in get_wave_state() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdkfd: Fix OOB memory exposure in get_wave_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ef144458f48d5589e36f1b3d83e83db2e5c5ba5

Vendor Advisories for CVE-2026-97496(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
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 45× in last 7d / 67× 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 08:54 UTCEG score recompute
  2. 2026-10-05 08:54 UTCVendor advisory
  3. 2026-10-05 08:54 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 21:31 UTCVendor advisory
  6. 2026-10-04 21:31 UTCGHSA enrichment
  7. 2026-10-04 10:11 UTCVendor advisory
  8. 2026-10-04 10:11 UTCGHSA enrichment
  9. 2026-10-03 22:51 UTCEG score recompute
  10. 2026-10-03 22:51 UTCVendor advisory
  11. 2026-10-03 22:51 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 11:30 UTCVendor advisory
  14. 2026-10-03 11:30 UTCGHSA enrichment
  15. 2026-10-03 01:28 UTCEG score recompute
  16. 2026-10-03 01:28 UTCVendor advisory
  17. 2026-10-03 01:28 UTCGHSA enrichment
  18. 2026-10-02 17:57 UTCEPSS rescore
  19. 2026-10-02 14:07 UTCVendor advisory
  20. 2026-10-02 14:07 UTCGHSA enrichment
  21. 2026-10-02 02:46 UTCEG score recompute
  22. 2026-10-02 02:46 UTCVendor advisory
  23. 2026-10-02 02:46 UTCGHSA enrichment
  24. 2026-10-01 19:51 UTCEPSS rescore
  25. 2026-10-01 15:16 UTCVendor advisory
Show 42 more
  1. 2026-10-01 15:16 UTCGHSA enrichment
  2. 2026-10-01 03:56 UTCVendor advisory
  3. 2026-10-01 03:56 UTCGHSA enrichment
  4. 2026-09-30 16:36 UTCEG score recompute
  5. 2026-09-30 16:36 UTCVendor advisory
  6. 2026-09-30 16:36 UTCGHSA enrichment
  7. 2026-09-30 15:04 UTCEPSS rescore
  8. 2026-09-30 04:08 UTCVendor advisory
  9. 2026-09-30 04:08 UTCGHSA enrichment
  10. 2026-09-29 16:47 UTCEG score recompute
  11. 2026-09-29 16:47 UTCVendor advisory
  12. 2026-09-29 16:47 UTCGHSA enrichment
  13. 2026-09-29 05:20 UTCEG score recompute
  14. 2026-09-29 05:20 UTCVendor advisory
  15. 2026-09-29 05:20 UTCGHSA enrichment
  16. 2026-09-28 18:00 UTCEG score recompute
  17. 2026-09-28 18:00 UTCVendor advisory
  18. 2026-09-28 18:00 UTCGHSA enrichment
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 13:52 UTCEPSS rescore
  21. 2026-09-28 06:24 UTCEG score recompute
  22. 2026-09-28 06:24 UTCGHSA enrichment
  23. 2026-09-28 05:47 UTCEG score recompute
  24. 2026-09-28 05:47 UTCGHSA enrichment
  25. 2026-09-28 01:22 UTCGHSA enrichment
  26. 2026-09-27 14:02 UTCEG score recompute
  27. 2026-09-27 14:02 UTCGHSA enrichment
  28. 2026-09-27 13:49 UTCEPSS rescore
  29. 2026-09-27 02:42 UTCEG score recompute
  30. 2026-09-27 02:42 UTCGHSA enrichment
  31. 2026-09-26 15:59 UTCEPSS rescore
  32. 2026-09-26 15:21 UTCGHSA enrichment
  33. 2026-09-26 04:01 UTCEG score recompute
  34. 2026-09-26 04:00 UTCGHSA enrichment
  35. 2026-09-25 16:37 UTCEG score recompute
  36. 2026-09-25 16:37 UTCGHSA enrichment
  37. 2026-09-25 05:17 UTCEG score recompute▲ 7.10
  38. 2026-09-25 05:17 UTCGHSA enrichment
  39. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  40. 2026-09-24 17:33 UTCNVD update
  41. 2026-09-24 16:27 UTCEG score recompute
  42. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97496?
CVE-2026-97496 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix OOB memory exposure in getwavestate() The getwavestate() function for v9 trusts cphqdcntlstacksize and cphqdcntlstackoffset values read directly from the MQD, which are written by GPU microcode and fully…
When was CVE-2026-97496 disclosed?
CVE-2026-97496 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-97496 actively exploited?
CVE-2026-97496 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97496?
CVE-2026-97496 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97496?
No fix for CVE-2026-97496 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-97496 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-97496

Explore →

Is Your Infrastructure Affected by CVE-2026-97496?

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

Book a Demo →Browse All CVEs