CVE-2026-98623: Linux kernel · drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in db5dd9f47b4df1be322f498d846e9a82940a7390 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
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 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in db5dd9f47b4df1be322f498d846e9a82940a7390, aff09d9e37e02dc60bde79035ac15b136d602259, a867abcfa85ab487066c3d3008a1ba905da04113 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 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
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | 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 is available and has been applied in multiple Linux kernel commits. Users should update their Linux kernel to a version including these fixes to remediate the vulnerability.
Description
A use-after-loop vulnerability in the Linux kernel's drm/nouveau/clk component was fixed. The issue arises when the function nvkm_clk_ustate_update uses a list cursor incorrectly if the loop exits without a break, leading to an invalid pointer dereference. This can be triggered from userspace via the 'pstate' debugfs file by requesting an invalid pstate id, causing an out-of-bounds read.
References
- git.kernel.org/stable/c/db5dd9f47b4df1be322f498d846e9a82940a7390 (opens in a new tab)
- git.kernel.org/stable/c/9d550924961f61a491dd95359c63494fa8a23d9f (opens in a new tab)
- git.kernel.org/stable/c/492e9cfa12f35f7946ea1b78a19f1f9337d62248 (opens in a new tab)
- git.kernel.org/stable/c/a867abcfa85ab487066c3d3008a1ba905da04113 (opens in a new tab)
- git.kernel.org/stable/c/5315c7bacfe274ddfe649d9556e9a341ffa812da (opens in a new tab)
- git.kernel.org/stable/c/0d096a7f7d79207490858dde731b16da5337e90c (opens in a new tab)
- git.kernel.org/stable/c/391517da7fd54ae40e4a7fe1cc696217343b0061 (opens in a new tab)
- git.kernel.org/stable/c/aff09d9e37e02dc60bde79035ac15b136d602259 (opens in a new tab)