CVE-2026-97900: Linux kernel · drm/drm_exec: fix up contended obj when num_objects is 0
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · 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.
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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by modifying drm_exec_prepare_array() to call drm_exec_lock_contended() when num_objects is zero. Users should apply the official kernel updates that include this fix. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended remediation.
Description
A vulnerability in the Linux kernel's drm_exec locking mechanism could cause an infinite loop when handling contended objects with zero num_objects. This occurs because drm_exec_prepare_array() returns success without properly clearing contention state when num_objects is zero, leading to a spin loop in certain driver operations such as amdgpu's userq signal/wait ioctls. The issue has been fixed by ensuring drm_exec_prepare_array() calls drm_exec_lock_contended() even when num_objects is zero to clear pending contention.
References
- ubuntu.com/security/CVE-2026-97900 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-97900 (opens in a new tab)
- git.kernel.org/stable/c/a565022c02f218ec9789c2baf4690792e7a48cbb (opens in a new tab)
- git.kernel.org/stable/c/159720704d9d652b64390c11fb971e15b0a78d23 (opens in a new tab)
- git.kernel.org/stable/c/831cd124ce99c3e61266bed30519d52f7c26abed (opens in a new tab)
- git.kernel.org/stable/c/f3e74866018dab793ebee1fdf0ef34f7271d1f8c (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-97900 (opens in a new tab)
- git.kernel.org/stable/c/506cfed91e50cc8055799480a2fde5a18f63a21c (opens in a new tab)