VulnerabilityPublished 25 Sep 2026Updated 21 Oct 2026

CVE-2026-97928: Linux kernel · drm/amdgpu: skip the VMID 0 flush for VRAM

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in 6593494733ccaf691db7bd13801583d188409607 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6593494733ccaf691db7bd13801583d188409607, 241d7450cf75969cea450eb3e740cb9682f69c2f, 87ceb8cba73d0b3c4025ff42495bccd8164acaed +1

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to 6593494733ccaf691db7bd13801583d188409607, 241d7450cf75969cea450eb3e740cb9682f69c2f, 87ceb8cba73d0b3c4025ff42495bccd8164acaed or 30dacb56f07283a1acb353ce81baef31f85396b0.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ a68c7eaa7a8ffdec9287ba1561a668d674c20a13, < 6593494733ccaf691db7bd13801583d188409607	Fixed in 6593494733ccaf691db7bd13801583d188409607
LinuxLinux	Affected ≥ a68c7eaa7a8ffdec9287ba1561a668d674c20a13, < 241d7450cf75969cea450eb3e740cb9682f69c2f	Fixed in 241d7450cf75969cea450eb3e740cb9682f69c2f
LinuxLinux	Affected ≥ a68c7eaa7a8ffdec9287ba1561a668d674c20a13, < 87ceb8cba73d0b3c4025ff42495bccd8164acaed	Fixed in 87ceb8cba73d0b3c4025ff42495bccd8164acaed
LinuxLinux	Affected ≥ a68c7eaa7a8ffdec9287ba1561a668d674c20a13, < 30dacb56f07283a1acb353ce81baef31f85396b0	Fixed in 30dacb56f07283a1acb353ce81baef31f85396b0
LinuxLinux	Affected =6.10	Fixed in–

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)

References

Community reviews

Loading reviews…