Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99147

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < 74b4d2370a9e2b77247063dfa05f452766102676
    • affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < 9dd91a22f076a4d19f14d82a5ab790c6bbaa073e
    • affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < 96d9996e5dbcfabed052c0d9377a382c95fed607
    • affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < 7a10cd79c4d9a90334fece32fef3a8e5b1a9727b
    • affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < 26401a4999f1596a515b2e704e7066ac09306488
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99147 badge
[![CVE-2026-99147](https://cveledger.app/badge/CVE-2026-99147.svg)](https://cveledger.app/cve/CVE-2026-99147)

Record last updated .