CVE-2026-99147

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

Published Oct 28, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Linux kernel DRM subsystem contains a flaw where a pre‑locked object is prematurely added to the array of locked objects while a reference to it is still active. If that object is destroyed during this period, the kernel may later attempt to operate on a freed area, triggering memory corruption or a BUG_ON in the driver when it adds a fence to the object. This vulnerability is an instance of CWE-617. The commit that resolves the issue keeps the pre‑locked object out of the locked array until the driver explicitly references it again.

Affected Systems

All Linux kernel releases that include the vulnerable DRM implementation are affected, and no specific version range is provided. Until a patch containing the fix is installed, any system running a kernel built before the change is potentially vulnerable.

Risk and Exploitability

The CVSS score is 5.5, and the EPSS score is < 1%. The vulnerability is not listed in CISA KEV, so the exploitation probability is uncertain. However, because the failure can corrupt kernel memory and enable arbitrary execution in kernel mode, a local adversary able to trigger contention in DRM drivers could potentially exploit it. The attack vector is not described in the advisory; it would likely involve interactions with graphics drivers that exercise the contested locking path.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Deploy the latest patched Linux kernel version that incorporates the fix for the DRM exec locking issue.
  • If a patch is not yet available, unload or disable kernel modules that use the DRM exec locking mechanism until an update is released.
  • Continuously monitor system logs for kernel panic messages or unexpected behavior related to DRM drivers, and take corrective action such as rolling back to a known stable kernel if the issue persists.

Generated by OpenCVE AI on October 30, 2026 at 05:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-617
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
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.
Title drm/exec: don't immediately add prelocked obj to array of locked objs
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:42 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 30, 2026, 1:21 PM
Severity
Moderate
Public date
Oct 28, 2026, 10:35 AM