---
id: "CVE-2026-99147"
kind: "vulnerability"
aliases: ["CVE-2026-99147"]
title: "Linux kernel: DRM exec lock handling can corrupt memory via fence slots"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["drm", "gpu-drivers", "infrastructure", "linux-kernel"]
not_affected_if: ["unknown"]
published_at: "2026-10-28T11:17:34+00:00"
first_seen_at: "2026-10-28T11:32:35+00:00"
updated_at: "2026-10-28T11:35:59+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99147", "first_seen_at": "2026-10-28T11:32:35+00:00"}]
---

# Linux kernel: DRM exec lock handling can corrupt memory via fence slots

In the Linux kernel's DRM exec locking helper, a pre-locked object that is about to be destroyed can be left out of the locked-object array, so a driver adding fences to all locked objects may hit a warning or BUG_ON. The sources describe this as a potential memory corruption issue in the graphics driver stack.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- Update the Linux kernel to a release that includes the upstream commit resolving 'drm/exec: don't immediately add prelocked obj to array of locked objs' (exact fixed version unknown from sources)

## Timeline

- 2026-10-28T11:32:35+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99147

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_