# CVE-2026-99147: drm/exec: don't immediately add prelocked obj to array of locked objs


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111278, BELL-CVE-2026-99147, DEBIAN-CVE-2026-99147, GHSA-f9vc-r5f2-m3x9, UBUNTU-CVE-2026-99147

## What is CVE-2026-99147?

CVE-2026-99147 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/exec: don't immediately add prelocked obj to array of locked objs

When a contention is detected the drm_exec object grabs a reference to
the contended object, unlocks all other objects and pre-locks the
contended one before anything else.

The problem is that it is possible that this pre-locked object was about
to be destroyed and drm_exec is now holding the last reference to it.

So we never actually see this pre-locked object again to be explicitly
locked and so also never reserve a slot for a dma_fence object on it.

Should the driver now use drm_exec_for_each_locked_object() to add a new
fence to all locked objects we eventually see a warning or even a
BUG_ON() to prevent random memory corruption.

Fix this by keeping the prelocked object out of the array of locked objs
until it was explicitly mentioned by the driver again.

If the prelocked object is never mentioned again by the driver
just unlock and drop the reference at the end of the locking loop.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99147 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99147 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99147 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-99147/ (Markdown: https://insights.sbomify.com/CVE-2026-99147/index.md)
```

## Sources

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

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