# CVE-2026-72090: accel/amdxdna: Use caller client for debug BO sync

> Incorrect client context usage in AMD XDNA driver debug buffer sync may cause logic errors or undefined behavior in kernel space.

- **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:** DEBIAN-CVE-2026-72090, GHSA-qqcm-w5c8-f3qv, UBUNTU-CVE-2026-72090

## What is CVE-2026-72090?

CVE-2026-72090 is a high-severity 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: Use caller client for debug BO sync

amdxdna_drm_sync_bo_ioctl() looks up args->handle in the ioctl caller's
drm_file. For SYNC_DIRECT_FROM_DEVICE, it then calls
amdxdna_hwctx_sync_debug_bo(), but passes abo->client.

amdxdna_hwctx_sync_debug_bo() uses the passed client both as the handle
namespace for debug_bo_hdl and as the owner of the hardware context xarray.
Those must match the file that supplied args->handle. The BO's stored
client pointer is object state, not the ioctl context.

Pass filp->driver_priv instead, matching the original handle lookup.

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


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

Apply the vendor's patch.

## Is CVE-2026-72090 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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