CVE-2026-97496

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-86094 (ENISA EUVD) · GHSA-qvg3-fh9p-wjpx (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 24, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
Patch available.
Web page

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
Web page

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
Web page

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

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 7× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 171 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 71 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-11-19 20:26 UTCEchelonGraph re-scored
  4. 2026-11-19 20:26 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  5. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-11-13 07:59 UTCEchelonGraph re-scored
  12. 2026-11-13 07:59 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  13. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-11-06 19:32 UTCEchelonGraph re-scored
  20. 2026-11-06 19:32 UTCVendor advisory
  21. 2026-11-06 19:32 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  22. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 75 more
  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-31 07:01 UTCEchelonGraph re-scored
  5. 2026-10-31 07:01 UTCVendor advisory
  6. 2026-10-31 07:01 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  7. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-25 13:47 UTCEchelonGraph re-scored
  14. 2026-10-24 18:33 UTCEchelonGraph re-scored
  15. 2026-10-24 18:33 UTCVendor advisory
  16. 2026-10-24 18:33 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  17. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-19 17:01 UTCEchelonGraph re-scored
  23. 2026-10-19 17:01 UTCVendor advisory
  24. 2026-10-19 17:01 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  25. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  26. 2026-10-18 02:56 UTCEchelonGraph re-scored
  27. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  28. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  32. 2026-10-13 04:03 UTCEchelonGraph re-scored
  33. 2026-10-13 04:03 UTCVendor advisory
  34. 2026-10-13 04:02 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  35. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  36. 2026-10-12 14:39 UTCEchelonGraph re-scored
  37. 2026-10-12 01:31 UTCVendor advisory
  38. 2026-10-12 01:31 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  39. 2026-10-11 19:10 UTCEchelonGraph re-scored
  40. 2026-10-11 16:26 UTCEchelonGraph re-scored
  41. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  42. 2026-10-11 13:38 UTCEchelonGraph re-scored
  43. 2026-10-11 13:06 UTCEchelonGraph re-scored
  44. 2026-10-11 13:06 UTCVendor advisory
  45. 2026-10-11 13:06 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  46. 2026-10-11 01:45 UTCEchelonGraph re-scored
  47. 2026-10-11 01:45 UTCVendor advisory
  48. 2026-10-11 01:45 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  49. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  50. 2026-10-10 14:23 UTCVendor advisory
  51. 2026-10-10 14:23 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  52. 2026-10-10 03:02 UTCEchelonGraph re-scored
  53. 2026-10-10 03:02 UTCVendor advisory
  54. 2026-10-10 03:02 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  55. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  56. 2026-10-09 15:41 UTCVendor advisory
  57. 2026-10-09 15:41 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  58. 2026-10-09 04:21 UTCEchelonGraph re-scored
  59. 2026-10-09 04:21 UTCVendor advisory
  60. 2026-10-09 04:21 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  61. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  62. 2026-10-08 17:00 UTCVendor advisory
  63. 2026-10-08 17:00 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  64. 2026-10-08 05:03 UTCVendor advisory
  65. 2026-10-08 05:03 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  66. 2026-10-07 17:42 UTCVendor advisory
  67. 2026-10-07 17:42 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  68. 2026-10-07 06:15 UTCVendor advisory
  69. 2026-10-07 06:15 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  70. 2026-10-06 18:55 UTCEchelonGraph re-scored
  71. 2026-10-06 18:55 UTCVendor advisory
  72. 2026-10-06 18:55 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1
  73. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  74. 2026-10-06 07:35 UTCVendor advisory
  75. 2026-10-06 07:35 UTCGHSA enrichmentGHSA-qvg3-fh9p-wjpx · GitHub severity HIGH · GitHub CVSS 7.1

Frequently asked(5)

What is CVE-2026-97496?
CVE-2026-97496 is a high-severity vulnerability; its CVE record was published on September 24, 2026. 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…
When was the CVE record for CVE-2026-97496 published?
The CVE record for CVE-2026-97496 was published on September 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 3, 2026; the record at its source may have been updated since.
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 (2nd 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?
A fix for CVE-2026-97496 is available: update to the fixed version the vendor names in its advisory. 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.