CVE-2026-68102

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

References (5)

Vendor Advisories for CVE-2026-68102(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 12× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 02:15 UTCGHSA enrichment
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 05:41 UTCGHSA enrichment
  6. 2026-08-17 05:26 UTCNVD update
  7. 2026-08-17 05:12 UTCGHSA enrichment
  8. 2026-08-17 05:05 UTCMITRE cvelistV5
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 06:36 UTCGHSA enrichment
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 10:03 UTCEG score recompute
  14. 2026-08-13 10:03 UTCGHSA enrichment
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-10 13:24 UTCNVD update
  17. 2026-08-10 12:22 UTCEG score recompute
  18. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68102?
CVE-2026-68102 is a publicly disclosed vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix aperture mapping leak amdgpupciremove() calls drmdevunplug() before invoking the driver fini routines. This causes drmdeventer() in amdgputtmfini() to always return false, so iounmap(aperbasekaddr) never runs on…
When was CVE-2026-68102 disclosed?
CVE-2026-68102 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68102 actively exploited?
CVE-2026-68102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.5% of all scored CVEs.
How do I remediate CVE-2026-68102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68102, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68102

Explore →

Is Your Infrastructure Affected by CVE-2026-68102?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs