drm/amdgpu: skip the VMID 0 flush for VRAM
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 241d7450cf75969cea450eb3e740cb9682f69c2f, Kernel 30dacb56f07283a1acb353ce81baef31f85396b0, Kernel 6593494733ccaf691db7bd13801583d188409607 and 1 more.
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)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.10, >=a68c7eaa7a8ffdec9287ba1561a668d674c20a13 <241d7450cf75969cea450eb3e740cb9682f69c2f, >=a68c7eaa7a8ffdec9287ba1561a668d674c20a13 <30dacb56f07283a1acb353ce81baef31f85396b0, >=a68c7eaa7a8ffdec9287ba1561a668d674c20a13 <6593494733ccaf691db7bd13801583d188409607, >=a68c7eaa7a8ffdec9287ba1561a668d674c20a13 <87ceb8cba73d0b3c4025ff42495bccd8164acaed | 241d7450cf75969cea450eb3e740cb9682f69c2f, 30dacb56f07283a1acb353ce81baef31f85396b0, 6593494733ccaf691db7bd13801583d188409607, 87ceb8cba73d0b3c4025ff42495bccd8164acaed |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket