Answer in brief
CVE-2026-97900 records a Unknown severity vulnerability in drm/drm_exec: fix up contended obj when num_objects is 0. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=09593216bff15866f95c8ad406cb7fdcec1ee40a <831cd124ce99c3e61266bed30519d52f7c26abed || >=09593216bff15866f95c8ad406cb7fdcec1ee40a <f3e74866018dab793ebee1fdf0ef34f7271d1f8c || >=09593216bff15866f95c8ad406cb7fdcec1ee40a <a565022c02f218ec9789c2baf4690792e7a48cbb || >=09593216bff15866f95c8ad406cb7fdcec1ee40a <159720704d9d652b64390c11fb971e15b0a78d23 | 831cd124ce99c3e61266bed30519d52f7c26abed, f3e74866018dab793ebee1fdf0ef34f7271d1f8c, a565022c02f218ec9789c2baf4690792e7a48cbb, 159720704d9d652b64390c11fb971e15b0a78d23 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.