CVE-2026-80728

Revert "drm/amdgpu: fix aperture mapping leak"

N/A
Published: September 3, 2026 at 08:21 AM UTC
Updated: October 30, 2026 at 01:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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 devres_release_all() unmaps the aperture before the DRM device release callback fires amdgpu_device_fini_sw(). IP sw_fini callbacks (e.g. vcn_v4_0_sw_fini) write to fw_shared through a pointer derived from aper_base_kaddr, causing a kernel page fault on probe failure / rollback: BUG: unable to handle page fault ... PMD 0 RIP: vcn_v4_0_sw_fini+0x7b/0x170 [amdgpu] Call Trace: amdgpu_device_fini_sw amdgpu_driver_release_kms devm_drm_dev_init_release devres_release_all This reverts commit d871e99879cb5fd1fa798b006b4888887e63a17a. (cherry picked from commit 336e0cd576817ac64a4b394ca2b3680029f3e37f)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.1916.12.1016.18.426.6.1486405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa67bc3647e418e23dc0d17604bdba634a73de809f7.1.68cf4724ea4f23c438af87a6cd0582a3372d30da9a343d028ad6c174da8dc6af560c51e6d140a6727ea772a440d56b285f4d491affac50ecd41f6b402f5988b5c300a32ff751724ffd33d5a8d5873e4a7
Vendor states this is fixed in 496846a9411136eb9e86ad4f4e62d751bd1e1db5 (fixed)
Vendor states this is fixed in 7380f1bfe9d7ed3a4ca9d99a5c4df840fff9af2a (fixed)
Vendor states this is fixed in 96d26143882f9cb47dcc1f3dd4e26d047e53ab9b (fixed)
Vendor states this is fixed in a2e326c52c4bcecc033cd3ca2733fdbe30fbf55d (fixed)
Vendor states this is fixed in b96c529cd2551b78316a4afa3237b2ed96ba03c8 (fixed)
Affected range stops below 6.12.104, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.18.45, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.152, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.1.9, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card