# CVE-2026-97496: drm/amdkfd: Fix OOB memory exposure in get_wave_state()

> An attacker can leak adjacent kernel memory via an out-of-bounds read in the AMD KFD driver, exposing sensitive data like KASLR pointers.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103965, BELL-CVE-2026-97496, DEBIAN-CVE-2026-97496, GHSA-qvg3-fh9p-wjpx, UBUNTU-CVE-2026-97496

## What is CVE-2026-97496?

CVE-2026-97496 is a high-severity vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-97496?


## How do I fix CVE-2026-97496?

Apply the vendor's patch.

## Is CVE-2026-97496 being exploited?

There is no known exploitation of CVE-2026-97496 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97496 and fix it if it is affected.

What it is: CVE-2026-97496 is a high-severity vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97496 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97496/ (Markdown: https://insights.sbomify.com/CVE-2026-97496/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97496
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97496
- OSV: https://osv.dev/vulnerability/CVE-2026-97496

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97496/
Summaries are generated and may contain mistakes; the official description above is the record.