{"id":"CVE-2026-68102","title":"drm/amdgpu: fix aperture mapping leak","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix aperture mapping leak\n\namdgpu_pci_remove() calls drm_dev_unplug() before invoking the driver\nfini routines. This causes drm_dev_enter() in amdgpu_ttm_fi…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < 8cf4724ea4f23c438af87a6cd0582a3372d30da9","Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < 67bc3647e418e23dc0d17604bdba634a73de809f","Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < a343d028ad6c174da8dc6af560c51e6d140a6727","Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < 6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa","Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < f5988b5c300a32ff751724ffd33d5a8d5873e4a7","Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < ea772a440d56b285f4d491affac50ecd41f6b402","Linux 5.13"],"published":"2026-08-10","updated":"2026-10-30","sourceUpdated":"2026-10-30T12:28:04.267Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-68102","references":[{"url":"https://git.kernel.org/stable/c/8cf4724ea4f23c438af87a6cd0582a3372d30da9"},{"url":"https://git.kernel.org/stable/c/67bc3647e418e23dc0d17604bdba634a73de809f"},{"url":"https://git.kernel.org/stable/c/a343d028ad6c174da8dc6af560c51e6d140a6727"},{"url":"https://git.kernel.org/stable/c/6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa"},{"url":"https://git.kernel.org/stable/c/f5988b5c300a32ff751724ffd33d5a8d5873e4a7"},{"url":"https://git.kernel.org/stable/c/ea772a440d56b285f4d491affac50ecd41f6b402"}],"tags":["cve.org"],"epss":0.00172,"epssPercentile":0.06666,"ingestedAt":"2026-11-05T15:02:32.433Z","slug":"CVE-2026-68102","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix aperture mapping leak\n\namdgpu_pci_remove() calls drm_dev_unplug() before invoking the driver\nfini routines. This causes drm_dev_enter() in amdgpu_ttm_fini() to\nalways return false, so iounmap(aper_base_kaddr) never runs on normal\ndriver unload, leaving an orphaned entry in the x86 PAT interval tree.\n\nOn connected_to_cpu hardware, the aperture is mapped write-back (WB) via\nioremap_cache(). On reload, IP discovery calls memremap(..., MEMREMAP_WC)\nover the same range. The WC vs WB conflict causes:\n\n  ioremap error for 0x..., requested 0x1, got 0x0\n  amdgpu: discovery failed: -2\n\nFix by switching to devres-managed mappings so cleanup is guaranteed\nregardless of drm_dev_enter() state:\n\n- connected_to_cpu path: devm_memremap(MEMREMAP_WB). For\n  IORESOURCE_SYSTEM_RAM ranges this takes the try_ram_remap() shortcut,\n  returning __va(offset) from the existing kernel direct map. No new\n  ioremap VA or PAT entry is created, so there is nothing to orphan.\n\n- dGPU path: devm_ioremap_wc() registers iounmap() as a devres action,\n  guaranteeing cleanup at device_del() time.\n\nAlso remove iounmap(aper_base_kaddr) from amdgpu_device_unmap_mmio()\nsince the mapping is now devres-owned.\n\nv2: Remove redundant x86_64 guard (Lijo)\n\n(cherry picked from commit d871e99879cb5fd1fa798b006b4888887e63a17a)\n\n## Affected\n\n- `Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < 8cf4724ea4f23c438af87a6cd0582a3372d30da9`\n- `Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < 67bc3647e418e23dc0d17604bdba634a73de809f`\n- `Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < a343d028ad6c174da8dc6af560c51e6d140a6727`\n- `Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < 6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa`\n- `Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < f5988b5c300a32ff751724ffd33d5a8d5873e4a7`\n- `Linux >= 9d0af8b4def0de6b734ec8db08e96da0458facb6 < ea772a440d56b285f4d491affac50ecd41f6b402`\n- `Linux 5.13`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}