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

CVE-2026-99147 is fixed in linux on 1 platform by DEBIAN-CVE-2026-99147 (version 6.12.115-2), released November 3, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-99147
- Priority: High
- CVSS: 7.1 (Moderate)
- EPSS: 0.0017
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Oct 28, 2026
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-99147

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

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 13.5 (trixie) | 6.12.115-2 | [DEBIAN-CVE-2026-99147](https://patchblox.com/security/data/fix/linux/debian-cve-2026-99147.md) | Nov 3, 2026 |

---

Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.