# drm/amdgpu: fix aperture mapping leak

CVE record · `CVE-2026-68102`

- **Identifiers:** `CVE-2026-68102`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 10 Aug 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 10 Aug 2026, 11:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `9d0af8b4def0de6b734ec8db08e96da0458facb6 to before 8cf4724ea4f23c438af87a6cd0582a3372d30da9` (git)
  - affected: `9d0af8b4def0de6b734ec8db08e96da0458facb6 to before 67bc3647e418e23dc0d17604bdba634a73de809f` (git)
  - affected: `9d0af8b4def0de6b734ec8db08e96da0458facb6 to before a343d028ad6c174da8dc6af560c51e6d140a6727` (git)
  - affected: `9d0af8b4def0de6b734ec8db08e96da0458facb6 to before 6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa` (git)
  - affected: `9d0af8b4def0de6b734ec8db08e96da0458facb6 to before f5988b5c300a32ff751724ffd33d5a8d5873e4a7` (git)
  - affected: `9d0af8b4def0de6b734ec8db08e96da0458facb6 to before ea772a440d56b285f4d491affac50ecd41f6b402` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.13`
  - unaffected: `before 5.13` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.148 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.101 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.42 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.6 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel amdgpu DRM driver had an aperture mapping leak: on normal unload the device's mapping of the aperture was never released, so a later driver reload could fail with a memory-mapping conflict and the GPU discovery step would error out. The source describes the trigger as a normal driver unload and reload, not an attack, and does not describe any attacker capability. Upgrade the Linux kernel to a version that includes the fix, such as one of the listed stable releases (6.1.191, 6.6.148, 6.12.101, or 6.18.42 or later in those series).

Written 12 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0017, the 6th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 10 Aug 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-68102](https://www.cve.org/CVERecord?id=CVE-2026-68102)
- [NVD: CVE-2026-68102](https://nvd.nist.gov/vuln/detail/CVE-2026-68102)

### References from the CNA

- <https://git.kernel.org/stable/c/8cf4724ea4f23c438af87a6cd0582a3372d30da9>
- <https://git.kernel.org/stable/c/67bc3647e418e23dc0d17604bdba634a73de809f>
- <https://git.kernel.org/stable/c/a343d028ad6c174da8dc6af560c51e6d140a6727>
- <https://git.kernel.org/stable/c/6405c4e75b3bcf0e72bd7a0ff5f1ed0c475e23aa>
- <https://git.kernel.org/stable/c/f5988b5c300a32ff751724ffd33d5a8d5873e4a7>
- <https://git.kernel.org/stable/c/ea772a440d56b285f4d491affac50ecd41f6b402>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-68102>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-68102/>. Everything for agents: <https://agentprime.io/llms.txt>.
