# CVE-2026-80608: accel/amdxdna: Fix iommu domain lifetime race during device removal

> A use-after-free race condition in the AMD XDNA kernel driver allows local attackers to potentially execute code or escalate privileges when force_iova mode is enabled.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-80608, GHSA-79jg-fp86-q5xg, UBUNTU-CVE-2026-80608

## What is CVE-2026-80608?

CVE-2026-80608 is a high-severity use after free vulnerability in Linux, published on 28 Aug 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:

accel/amdxdna: Fix iommu domain lifetime race during device removal

When force_iova mode is enabled, amdxdna_remove() frees xdna->domain. If
amdxdna_gem_obj_free() is called after device removal, it may attempt to
access xdna->domain, resulting in a use-after-free.

Fix the race by adding freeing xdna->domain as a managed release action,
so its lifetime is managed by DRM and remains valid until all managed
resources are released.

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


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

Apply the vendor's patch.

## Is CVE-2026-80608 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80608 is a high-severity use after free vulnerability in Linux, published on 28 Aug 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-80608 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-80608/ (Markdown: https://insights.sbomify.com/CVE-2026-80608/index.md)
```

## Sources

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

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