# CVE-2026-80728: Revert "drm/amdgpu: fix aperture mapping leak"

> A kernel page fault in the amdgpu driver during probe failure allows local attackers to cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** AZL-99059, BELL-CVE-2026-80728, DEBIAN-CVE-2026-80728, GHSA-gr66-4v49-m3fh, UBUNTU-CVE-2026-80728

## What is CVE-2026-80728?

CVE-2026-80728 is a vulnerability in Linux, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Revert "drm/amdgpu: fix aperture mapping leak"

devres teardown is LIFO. The aperture devres node was registered after
the DRM device node, so devres_release_all() unmaps the aperture before
the DRM device release callback fires amdgpu_device_fini_sw(). IP
sw_fini callbacks (e.g. vcn_v4_0_sw_fini) write to fw_shared through a
pointer derived from aper_base_kaddr, causing a kernel page fault on
probe failure / rollback:

  BUG: unable to handle page fault ... PMD 0
  RIP: vcn_v4_0_sw_fini+0x7b/0x170 [amdgpu]
  Call Trace:
    amdgpu_device_fini_sw
    amdgpu_driver_release_kms
    devm_drm_dev_init_release
    devres_release_all

This reverts commit d871e99879cb5fd1fa798b006b4888887e63a17a.

(cherry picked from commit 336e0cd576817ac64a4b394ca2b3680029f3e37f)

## Which versions are affected by CVE-2026-80728?


## How do I fix CVE-2026-80728?

Apply the vendor's patch.

## Is CVE-2026-80728 being exploited?

There is no known exploitation of CVE-2026-80728 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80728 and fix it if it is affected.

What it is: CVE-2026-80728 is a vulnerability in Linux, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80728 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80728/ (Markdown: https://insights.sbomify.com/CVE-2026-80728/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80728
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80728
- OSV: https://osv.dev/vulnerability/CVE-2026-80728

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80728/
Summaries are generated and may contain mistakes; the official description above is the record.