---
id: CVE-2026-97900
title: |-
  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 i…
summary: |-
  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 i…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 09593216bff15866f95c8ad406cb7fdcec1ee40a <
    831cd124ce99c3e61266bed30519d52f7c26abed
  - >-
    Linux >= 09593216bff15866f95c8ad406cb7fdcec1ee40a <
    f3e74866018dab793ebee1fdf0ef34f7271d1f8c
  - >-
    Linux >= 09593216bff15866f95c8ad406cb7fdcec1ee40a <
    a565022c02f218ec9789c2baf4690792e7a48cbb
  - >-
    Linux >= 09593216bff15866f95c8ad406cb7fdcec1ee40a <
    159720704d9d652b64390c11fb971e15b0a78d23
  - Linux 6.6
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T11:17:16.787'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97900'
references:
  - url: 'https://git.kernel.org/stable/c/159720704d9d652b64390c11fb971e15b0a78d23'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/831cd124ce99c3e61266bed30519d52f7c26abed'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a565022c02f218ec9789c2baf4690792e7a48cbb'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f3e74866018dab793ebee1fdf0ef34f7271d1f8c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-25T11:06:38.896Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.