CVE-2026-80728: Revert "drm/amdgpu: fix aperture mapping leak"
In the Linux kernel, the following vulnerability has been resolved:
Revert "drm/amdgpu: fix aperture mapping leak"
devres teardown is LIFO. The aperture devres node was registered after the DRM device node, so devresreleaseall() unmaps the aperture before the DRM device release callback fires amdgpudevicefinisw(). IP swfini callbacks (e.g. vcnv40swfini) write to fwshared through a pointer derived from aperbasekaddr, causing a kernel page fault on probe failure / rollback:
BUG: unable to handle page fault ... PMD 0 RIP: vcnv40swfini+0x7b/0x170 [amdgpu] Call Trace: amdgpudevicefinisw amdgpudriverreleasekms devmdrmdevinitrelease devresreleaseall
This reverts commit d871e99879cb5fd1fa798b006b4888887e63a17a.
(cherry picked from commit 336e0cd576817ac64a4b394ca2b3680029f3e37f)
Event History
Frequently Asked Questions
Under what circumstances can this issue cause a system failure?
The fault occurs during AMDGPU probe failure or rollback, when devres teardown unmaps the aperture before the DRM device release callback runs. Subsequent IP software-finalization callbacks can then access firmware-shared memory through the unmapped aperture pointer, causing a kernel page fault.
What component and cleanup path are involved?
The issue is in the Linux kernel AMDGPU DRM driver. The affected cleanup sequence is devres_release_all(), followed by the DRM device release path through amdgpu_driver_release_kms() and amdgpu_device_fini_sw().
What change addresses the problem?
The resolved change reverts the earlier "drm/amdgpu: fix aperture mapping leak" commit. The supplied references identify stable commits containing that revert.