CVE-2026-97900

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

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.

Key facts

Published
25 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.133% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 09593216bff15866f95c8ad406cb7fdcec1ee40a up to but excluding 506cfed91e50cc8055799480a2fde5a18f63a21c (affected)
  • 09593216bff15866f95c8ad406cb7fdcec1ee40a up to but excluding 831cd124ce99c3e61266bed30519d52f7c26abed (affected)
  • 09593216bff15866f95c8ad406cb7fdcec1ee40a up to but excluding f3e74866018dab793ebee1fdf0ef34f7271d1f8c (affected)
  • 09593216bff15866f95c8ad406cb7fdcec1ee40a up to but excluding a565022c02f218ec9789c2baf4690792e7a48cbb (affected)
  • 09593216bff15866f95c8ad406cb7fdcec1ee40a up to but excluding 159720704d9d652b64390c11fb971e15b0a78d23 (affected)
LinuxLinux
  • Default status: affected
  • 6.6 (affected)
  • 0 up to but excluding 6.6 (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References