# CVE-2026-72091: accel/amdxdna: reject user command submission without a command BO

> A local attacker with access to the AMD NPU device node can trigger a kernel null pointer dereference, causing a system crash.

- **Severity:** Not scored
- **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:** 15 Oct 2026
- **Also known as:** BELL-CVE-2026-72091, DEBIAN-CVE-2026-72091, GHSA-jvc7-qr5g-mx5f, UBUNTU-CVE-2026-72091

## What is CVE-2026-72091?

CVE-2026-72091 is a 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: reject user command submission without a command BO

amdxdna_drm_submit_execbuf() passes the user-supplied command BO handle
straight into amdxdna_cmd_submit() with drv_cmd == NULL. When the handle
is AMDXDNA_INVALID_BO_HANDLE (0), the block that fetches job->cmd_bo is
skipped, leaving it NULL, and no check rejects it on the user path (the
!job->cmd_bo guard lives inside the != INVALID branch).

The job is then armed and pushed to the DRM scheduler.
aie2_sched_job_run() takes the drv_cmd == NULL path and calls
amdxdna_cmd_set_state(job->cmd_bo) -> amdxdna_gem_vmap(NULL) ->
to_gobj(NULL)->dev, a NULL pointer dereference in the drm_sched worker.
A process with access to the accel node on a system with a probed AMD NPU
can trigger a kernel oops with a single AMDXDNA_EXEC_CMD ioctl
(cmd_handles = 0).

Only internal driver commands (SYNC_DEBUG_BO / ATTACH_DEBUG_BO)
legitimately pass AMDXDNA_INVALID_BO_HANDLE, and they always set drv_cmd.
Reject the invalid handle for user submissions (drv_cmd == NULL) at the
submit choke point so every user path is covered.

Found by 0sec automated security-research tooling (https://0sec.ai).

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


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

Apply the vendor's patch.

## Is CVE-2026-72091 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72091 is a 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-72091 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-72091/ (Markdown: https://insights.sbomify.com/CVE-2026-72091/index.md)
```

## Sources

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

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