# CVE-2026-93047: drm/v3d: Associate BOs with every job that accesses them

> A race condition in the Linux kernel v3d driver allows local attackers to cause data corruption by reading buffer objects while another context writes them.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102056, BELL-CVE-2026-93047, DEBIAN-CVE-2026-93047, GHSA-75w8-rpch-q4h9, UBUNTU-CVE-2026-93047

## What is CVE-2026-93047?

CVE-2026-93047 is a vulnerability in Linux, published on 17 Sep 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:

drm/v3d: Associate BOs with every job that accesses them

A submission can expand into a chain of jobs (e.g. bin + render + cache
clean). Implicit synchronization in v3d_submit_lock_reservations() is gated
on each job's bo[], but the BO list was only ever attached to the last job
of the chain. When that last job is a trailing CACHE_CLEAN job, the job
that actually consumes the BOs (that is, a RENDER or CSD job) was left with
bo_count == 0 and picked up no implicit dependencies. It could therefore
be dispatched to the hardware and read a BO while another context was still
writing it, leading to data corruption.

Attach the BOs to the job that consumes them, so (1) it acquires the
correct implicit dependencies during reservation locking and (2) they are
kept mapped until the end of the submission. Give it references to all
consuming job's BOs through v3d_job_reference_bos() instead of looking the
handles up a second time; that avoids a redundant lookup and guarantees
both jobs reference the exact same objects.

As the CACHE_CLEAN job now carries a BO array as well, add a per-job
`has_implicit_dep` flag so that only the consuming jobs take implicit
dependencies. The CACHE_CLEAN job (a global flush) and the BIN job (binning
waiting on another context is not a realistic scenario) are excluded.

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


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

Apply the vendor's patch.

## Is CVE-2026-93047 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93047 is a vulnerability in Linux, published on 17 Sep 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-93047 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-93047/ (Markdown: https://insights.sbomify.com/CVE-2026-93047/index.md)
```

## Sources

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

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