CVE-2026-97900

published 25 Sep 2026 · updated 20 Nov 2026

drm/drm_exec: fix up contended obj when num_objects is 0

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f3e74866018dab793ebee1fdf0ef34f7271d1f8c, Kernel 159720704d9d652b64390c11fb971e15b0a78d23, Kernel 506cfed91e50cc8055799480a2fde5a18f63a21c and 6 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=09593216bff15866f95c8ad406cb7fdcec1ee40a <f3e74866018dab793ebee1fdf0ef34f7271d1f8c, >=09593216bff15866f95c8ad406cb7fdcec1ee40a <159720704d9d652b64390c11fb971e15b0a78d23, >=09593216bff15866f95c8ad406cb7fdcec1ee40a <506cfed91e50cc8055799480a2fde5a18f63a21c, >=09593216bff15866f95c8ad406cb7fdcec1ee40a <831cd124ce99c3e61266bed30519d52f7c26abed, >=09593216bff15866f95c8ad406cb7fdcec1ee40a <a565022c02f218ec9789c2baf4690792e7a48cbb, =6.6f3e74866018dab793ebee1fdf0ef34f7271d1f8c, 159720704d9d652b64390c11fb971e15b0a78d23, 506cfed91e50cc8055799480a2fde5a18f63a21c, 831cd124ce99c3e61266bed30519d52f7c26abed, a565022c02f218ec9789c2baf4690792e7a48cbb
linux-kernel: Kernel>=6.19.0 <7.2.7, >=6.6.0 <6.6.158, >=6.7.0 <6.12.111, >=6.13.0 <6.18.537.2.7, 6.6.158, 6.12.111, 6.18.53

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97900 severity on Zeptric[![CVE-2026-97900](https://zeptric.io/badge/cve/CVE-2026-97900.svg)](https://zeptric.io/cve/CVE-2026-97900)