VulnerabilityPublished 10 Aug 2026Updated 30 Oct 2026

CVE-2026-68102: Linux kernel · drm/amdgpu: fix aperture mapping leak

Source GCVE Database

Compare

Authoritative record:CVE-2026-68102· Medium

Not known to be exploited · fixed in f5988b5c300a32ff751724ffd33d5a8d5873e4a7 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in f5988b5c300a32ff751724ffd33d5a8d5873e4a7, ea772a440d56b285f4d491affac50ecd41f6b402, a343d028ad6c174da8dc6af560c51e6d140a6727 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-vhc7-6hrm-49vv

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 9d0af8b4def0de6b734ec8db08e96da0458facb6, < f5988b5c300a32ff751724ffd33d5a8d5873e4a7	Fixed in f5988b5c300a32ff751724ffd33d5a8d5873e4a7
LinuxLinux	Affected ≥ 9d0af8b4def0de6b734ec8db08e96da0458facb6, < ea772a440d56b285f4d491affac50ecd41f6b402	Fixed in ea772a440d56b285f4d491affac50ecd41f6b402
LinuxLinux	Affected ≥ 9d0af8b4def0de6b734ec8db08e96da0458facb6, < a343d028ad6c174da8dc6af560c51e6d140a6727	Fixed in a343d028ad6c174da8dc6af560c51e6d140a6727
LinuxLinux	Affected ≥ 9d0af8b4def0de6b734ec8db08e96da0458facb6, < 6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa	Fixed in 6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa
LinuxLinux	Affected ≥ 9d0af8b4def0de6b734ec8db08e96da0458facb6, < 67bc3647e418e23dc0d17604bdba634a73de809f	Fixed in 67bc3647e418e23dc0d17604bdba634a73de809f
LinuxLinux	Affected ≥ 9d0af8b4def0de6b734ec8db08e96da0458facb6, < 8cf4724ea4f23c438af87a6cd0582a3372d30da9	Fixed in 8cf4724ea4f23c438af87a6cd0582a3372d30da9

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)

References

Community reviews

Loading reviews…