CVE-2026-68102drm/amdgpu: fix aperture mapping leak
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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)
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 9d0af8b4def0de6b734ec8db08e96da0458facb6 – < 8cf4724ea4f23c438af87a6cd0582a3372d30da9
- affected 9d0af8b4def0de6b734ec8db08e96da0458facb6 – < 67bc3647e418e23dc0d17604bdba634a73de809f
- affected 9d0af8b4def0de6b734ec8db08e96da0458facb6 – < a343d028ad6c174da8dc6af560c51e6d140a6727
- affected 9d0af8b4def0de6b734ec8db08e96da0458facb6 – < 6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa
- affected 9d0af8b4def0de6b734ec8db08e96da0458facb6 – < f5988b5c300a32ff751724ffd33d5a8d5873e4a7
- affected 9d0af8b4def0de6b734ec8db08e96da0458facb6 – < ea772a440d56b285f4d491affac50ecd41f6b402
- affected 5.13
- unaffected < 5.13
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/8cf4724ea4f23c438af87a6cd0582a3372d30da9 (opens in a new tab)
- https://git.kernel.org/stable/c/67bc3647e418e23dc0d17604bdba634a73de809f (opens in a new tab)
- https://git.kernel.org/stable/c/a343d028ad6c174da8dc6af560c51e6d140a6727 (opens in a new tab)
- https://git.kernel.org/stable/c/6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa (opens in a new tab)
- https://git.kernel.org/stable/c/f5988b5c300a32ff751724ffd33d5a8d5873e4a7 (opens in a new tab)
- https://git.kernel.org/stable/c/ea772a440d56b285f4d491affac50ecd41f6b402 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55483 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68102)Record last updated .