CVE-2026-97900drm/drm_exec: fix up contended obj when num_objects is 0
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: drm/drm_exec: fix up contended obj when num_objects is 0 drm_exec_prepare_array() silently returns success without calling drm_exec_lock_contended() when num_objects is zero. This breaks the invariant upheld by drm_exec_lock_obj(), where every entry point into the locking sequence must first attempt to lock any previously contended object before proceeding. Drivers that chain multiple drm_exec_prepare_array() calls per drm_exec_until_all_locked() iteration (e.g. amdgpu's userq signal/wait ioctls, which prepare separate read and write BO arrays) can pass an empty array for one of the two calls. If contention is hit while preparing the non-empty array, exec->contended is set and the loop retries; on retry, the empty-array call preceding it is a no-op that never clears exec->contended, so drm_exec_retry_on_contention() immediately jumps back to the top of the loop without ever reaching the call that would resolve the contention. This spins forever. Fix it by having drm_exec_prepare_array() call drm_exec_lock_contended() directly when num_objects is zero, so a pending contended object dont loop infinitely.
Timeline
ID reserved
By Linux
Published
- 24 days later
· 24 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 94% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < 506cfed91e50cc8055799480a2fde5a18f63a21c
- affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < 831cd124ce99c3e61266bed30519d52f7c26abed
- affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < f3e74866018dab793ebee1fdf0ef34f7271d1f8c
- affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < a565022c02f218ec9789c2baf4690792e7a48cbb
- affected 09593216bff15866f95c8ad406cb7fdcec1ee40a – < 159720704d9d652b64390c11fb971e15b0a78d23
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/506cfed91e50cc8055799480a2fde5a18f63a21c (opens in a new tab)
- https://git.kernel.org/stable/c/831cd124ce99c3e61266bed30519d52f7c26abed (opens in a new tab)
- https://git.kernel.org/stable/c/f3e74866018dab793ebee1fdf0ef34f7271d1f8c (opens in a new tab)
- https://git.kernel.org/stable/c/a565022c02f218ec9789c2baf4690792e7a48cbb (opens in a new tab)
- https://git.kernel.org/stable/c/159720704d9d652b64390c11fb971e15b0a78d23 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86754 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97900)Record last updated .