drm/drm_exec: fix up contended obj when num_objects is 0
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.
CVE-2026-97900
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-97900
Linux
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Linux
Source reference: /containers/cna/affected/1/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "09593216bff15866f95c8ad406cb7fdcec1ee40a",
"lessThan": "506cfed91e50cc8055799480a2fde5a18f63a21c",
"versionType": "git"
},
{
"status": "affected",
"version": "09593216bff15866f95c8ad406cb7fdcec1ee40a",
"lessThan": "831cd124ce99c3e61266bed30519d52f7c26abed",
"versionType": "git"
},
{
"status": "affected",
"version": "09593216bff15866f95c8ad406cb7fdcec1ee40a",
"lessThan": "f3e74866018dab793ebee1fdf0ef34f7271d1f8c",
"versionType": "git"
},
{
"status": "affected",
"version": "09593216bff15866f95c8ad406cb7fdcec1ee40a",
"lessThan": "a565022c02f218ec9789c2baf4690792e7a48cbb",
"versionType": "git"
},
{
"status": "affected",
"version": "09593216bff15866f95c8ad406cb7fdcec1ee40a",
"lessThan": "159720704d9d652b64390c11fb971e15b0a78d23",
"versionType": "git"
}
],
"programFiles": [
"drivers/gpu/drm/drm_exec.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.6"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.6",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.111",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.53",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.7",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/gpu/drm/drm_exec.c"
],
"defaultStatus": "affected"
}
]- Related CVEs
- CVE-2026-97900
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #38058 · Revision 1
- Added to Heist Feed
- Publisher date