drm/amdgpu: skip the VMID 0 flush for VRAM
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.114, 6.18.57, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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)
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From a68c7eaa7a8ffdec9287ba1561a668d674c20a13 · fixed in 6593494733ccaf691db7bd13801583d188409607; From a68c7eaa7a8ffdec9287ba1561a668d674c20a13 · fixed in 30dacb56f07283a1acb353ce81baef31f85396b0; From a68c7eaa7a8ffdec9287ba1561a668d674c20a13 · fixed in 241d7450cf75969cea450eb3e740cb9682f69c2f; From a68c7eaa7a8ffdec9287ba1561a668d674c20a13 · fixed in 87ceb8cba73d0b3c4025ff42495bccd8164acaed
- Linux Linux
6.10
- KernelLinux
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