7.3

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

Received
AliasesDEBIAN-CVE-2026-99147UBUNTU-CVE-2026-99147
Published 28-10-2026Last modified 30-10-2026

Vulnerability summary

CVE-2026-99147 is a high (CVSS 7.3) vulnerability in linux. EPSS estimates a 0.17% chance of exploitation in the next 30 days, higher than 7% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7.3, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.3/10
010
High · v4.0 (OSV · Ubuntu), selected by version preference
EPSS score
0.17%
0%100%
Low · Change unavailable
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 5 · Related 2

Timeline

  1. 28-10-2026
    PublishedVulnerability first disclosed.
  2. 30-10-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

1 score · 1 source · 1 version

EPSS trend

Probability

0.17%

Chance of exploitation in the next 30 days

Percentile

7%

Versus all other CVEs

30-day change

Change unavailable

Change unavailable

29-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu169 products
  • linuxAll versions (No fix recorded) | < 6.8.0-151.151 | < 7.3.0-10.10 | < 7.0.0-44.44
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1070.76 | < 7.3.0-1004.4 | < 7.0.0-1018.19
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linuxAll versions (No fix recorded) | < 6.12.115-2 | < 7.2.13-1
  • linux-6.12< 6.12.115-2~deb12u1
Linux1 product
  • linux≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < 74b4d2370a9e2b77247063dfa05f452766102676 | ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < 9dd91a22f076a4d19f14d82a5ab790c6bbaa073e | ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < 96d9996e5dbcfabed052c0d9377a382c95fed607 | ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < 7a10cd79c4d9a90334fece32fef3a8e5b1a9727b | ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < 26401a4999f1596a515b2e704e7066ac09306488 | 6.6

3 vendors · 172 products

References

10 links