drm/amdgpu: fix aperture mapping leak
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f5988b5c300a32ff751724ffd33d5a8d5873e4a7, Kernel 6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa, Kernel 67bc3647e418e23dc0d17604bdba634a73de809f and 8 more.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix aperture mapping leak amdgpu_pci_remove() calls drm_dev_unplug() before invoking the driver fini routines. This causes drm_dev_enter() in amdgpu_ttm_fini() to always return false, so iounmap(aper_base_kaddr) never runs on normal driver unload, leaving an orphaned entry in the x86 PAT interval tree. On connected_to_cpu hardware, the aperture is mapped write-back (WB) via ioremap_cache(). On reload, IP discovery calls memremap(..., MEMREMAP_WC) over the same range. The WC vs WB conflict causes: ioremap error for 0x..., requested 0x1, got 0x0 amdgpu: discovery failed: -2 Fix by switching to devres-managed mappings so cleanup is guaranteed regardless of drm_dev_enter() state: - connected_to_cpu path: devm_memremap(MEMREMAP_WB). For IORESOURCE_SYSTEM_RAM ranges this takes the try_ram_remap() shortcut, returning __va(offset) from the existing kernel direct map. No new ioremap VA or PAT entry is created, so there is nothing to orphan. - dGPU path: devm_ioremap_wc() registers iounmap() as a devres action, guaranteeing cleanup at device_del() time. Also remove iounmap(aper_base_kaddr) from amdgpu_device_unmap_mmio() since the mapping is now devres-owned. v2: Remove redundant x86_64 guard (Lijo) (cherry picked from commit d871e99879cb5fd1fa798b006b4888887e63a17a)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=9d0af8b4def0de6b734ec8db08e96da0458facb6 <f5988b5c300a32ff751724ffd33d5a8d5873e4a7, >=9d0af8b4def0de6b734ec8db08e96da0458facb6 <6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa, >=9d0af8b4def0de6b734ec8db08e96da0458facb6 <67bc3647e418e23dc0d17604bdba634a73de809f, >=9d0af8b4def0de6b734ec8db08e96da0458facb6 <8cf4724ea4f23c438af87a6cd0582a3372d30da9, >=9d0af8b4def0de6b734ec8db08e96da0458facb6 <a343d028ad6c174da8dc6af560c51e6d140a6727, >=9d0af8b4def0de6b734ec8db08e96da0458facb6 <ea772a440d56b285f4d491affac50ecd41f6b402, =5.13 | f5988b5c300a32ff751724ffd33d5a8d5873e4a7, 6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa, 67bc3647e418e23dc0d17604bdba634a73de809f, 8cf4724ea4f23c438af87a6cd0582a3372d30da9, a343d028ad6c174da8dc6af560c51e6d140a6727, ea772a440d56b285f4d491affac50ecd41f6b402 |
| linux-kernel: Kernel | >=6.13.0 <6.18.42, >=6.19.0 <7.1.6, >=6.2.0 <6.6.148, >=6.7.0 <6.12.101, >=5.13.0 <6.1.191 | 6.18.42, 7.1.6, 6.6.148, 6.12.101, 6.1.191 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket