VulnerabilityPublished 25 Sep 2026Updated 19 Oct 2026

CVE-2026-97900: Linux kernel · drm/drm_exec: fix up contended obj when num_objects is 0

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f3e74866018dab793ebee1fdf0ef34f7271d1f8c : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:36 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f3e74866018dab793ebee1fdf0ef34f7271d1f8c, a565022c02f218ec9789c2baf4690792e7a48cbb, 159720704d9d652b64390c11fb971e15b0a78d23 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < f3e74866018dab793ebee1fdf0ef34f7271d1f8c	Fixed in f3e74866018dab793ebee1fdf0ef34f7271d1f8c
LinuxLinux	Affected ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < a565022c02f218ec9789c2baf4690792e7a48cbb	Fixed in a565022c02f218ec9789c2baf4690792e7a48cbb
LinuxLinux	Affected ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < 159720704d9d652b64390c11fb971e15b0a78d23	Fixed in 159720704d9d652b64390c11fb971e15b0a78d23
LinuxLinux	Affected ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < 831cd124ce99c3e61266bed30519d52f7c26abed	Fixed in 831cd124ce99c3e61266bed30519d52f7c26abed
LinuxLinux	Affected ≥ 09593216bff15866f95c8ad406cb7fdcec1ee40a, < 506cfed91e50cc8055799480a2fde5a18f63a21c	Fixed in 506cfed91e50cc8055799480a2fde5a18f63a21c
LinuxLinux	Affected =6.6	Fixed in–

AI-suggested

A fix is available in the Linux kernel as indicated by the fixed commit versions. Users and administrators should update to a Linux kernel version that includes these fixes to resolve the infinite loop issue. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's drm subsystem was fixed where drm_exec_prepare_array() did not properly handle the case when num_objects is zero, causing an infinite loop during contention handling. This issue affected drivers like amdgpu that chain multiple drm_exec_prepare_array() calls and could lead to a spin loop under contention conditions.

Impact

This vulnerability can cause an infinite spin loop in the kernel when contention occurs during drm_exec_prepare_array() calls with empty arrays, potentially leading to denial of service by CPU resource exhaustion in affected drivers such as amdgpu.

Summary

The Linux kernel's drm_exec_prepare_array() function silently returns success without calling drm_exec_lock_contended() when num_objects is zero, breaking the locking sequence invariant. Drivers that chain multiple drm_exec_prepare_array() calls per drm_exec_until_all_locked() iteration, such as amdgpu's userq signal/wait ioctls, can pass an empty array for one call. If contention occurs on the non-empty array, exec->contended is set and the loop retries; however, the empty-array call preceding it does not clear exec->contended, causing drm_exec_retry_on_contention() to loop infinitely. The fix involves calling drm_exec_lock_contended() directly when num_objects is zero to prevent infinite spinning on a pending contended object.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 13:36 UTC

Technical details

References

Community reviews

Related threats