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

> A flaw in the amdgpu driver causes a spurious SDMA flush that can wedge the engine, leading to denial of service on GFX11 hardware.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-97928, DEBIAN-CVE-2026-97928, GHSA-x75f-rq9r-qmq7, UBUNTU-CVE-2026-97928

## What is CVE-2026-97928?

CVE-2026-97928 is a denial of service vulnerability in Linux, published on 25 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/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)

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


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

Apply the vendor's patch.

## Is CVE-2026-97928 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97928 is a denial of service vulnerability in Linux, published on 25 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-97928 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-97928/ (Markdown: https://insights.sbomify.com/CVE-2026-97928/index.md)
```

## Sources

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

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