# CVE-2026-72093: accel/amdxdna: Fix use-after-free in amdxdna_gem_dmabuf_mmap()

> A use-after-free in the AMD XDNA accelerator driver allows attackers to execute arbitrary code or escalate privileges via double-free logic.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72093, DEBIAN-CVE-2026-72093, GHSA-6xqj-5m3m-7w3w, UBUNTU-CVE-2026-72093

## What is CVE-2026-72093?

CVE-2026-72093 is a high-severity use after free vulnerability in Linux, published on 15 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 use-after-free in amdxdna_gem_dmabuf_mmap()

When vm_insert_pages() fails, the error path calls vma->vm_ops->close(vma)
which internally calls drm_gem_vm_close() → drm_gem_object_put(),
releasing the GEM object reference acquired at the start of the function.
However, the close_vma label then falls through to put_obj, which calls
drm_gem_object_put() a second time on the same object.

If the first put releases the last reference, the object is freed and the
second put accesses freed memory, causing a use-after-free.

Fix by returning directly from close_vma instead of falling through to
put_obj, since the close handler already performs all necessary cleanup
including the object put.

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


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

Apply the vendor's patch.

## Is CVE-2026-72093 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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