Live › vulnerability › CVE-2026-99147
Go to dashboardIn 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
Systems running Linux kernels with DRM graphics drivers that use the drm_exec locking helper and reserve fence slots on contended objects. The sources do not say which drivers or kernel versions are affected, so unknown whether a given machine is exposed.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99147")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.