# CVE-2026-72092: accel/amdxdna: reject command submission on devices without a submit op

> A local attacker can crash the Linux kernel by triggering a null pointer dereference in the AMD XDNA driver via a specific ioctl on unsupported devices.

- **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:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72092, DEBIAN-CVE-2026-72092, GHSA-phpf-xwr2-r7xq, UBUNTU-CVE-2026-72092

## What is CVE-2026-72092?

CVE-2026-72092 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 command submission on devices without a submit op

amdxdna_cmd_submit() calls xdna->dev_info->ops->cmd_submit()
unconditionally, but only aie2_dev_ops defines that callback.
aie4_vf_ops (the AIE4 SR-IOV virtual function) does not, so a user
AMDXDNA_EXEC_CMD ioctl on an AIE4 device reaches a NULL function-pointer
call and oopses the kernel. AIE4 submits work through a mapped user queue
and doorbell, not this ioctl path.

Reject the submission early with -EOPNOTSUPP when the device provides no
cmd_submit op, so the shared EXEC ioctl is a clean no-op on such devices.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-72092 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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