CVE-2026-98623: Linux kernel · drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:28 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
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
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.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update If list_for_each_entry() exits without hitting a break then "pstate" is not a valid pstate pointer. Introduce a "found" variable instead. The check is reachable from userspace: nvkm_clk_ustate_update() takes the pstate id straight from the 'pstate' debugfs file, so requesting an id that is not in clk->states - or any id at all when the perf tables are broken and the list is empty - makes the pstate->pstate != req test dereference the list head cast to a struct nvkm_pstate, which is an out-of-bounds read. [Francesco: rebased on drm-misc-next, expanded the commit message]
References
- ubuntu.com/security/CVE-2026-98623 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98623 (opens in a new tab)
- git.kernel.org/stable/c/9d550924961f61a491dd95359c63494fa8a23d9f (opens in a new tab)
- git.kernel.org/stable/c/0d096a7f7d79207490858dde731b16da5337e90c (opens in a new tab)
- git.kernel.org/stable/c/db5dd9f47b4df1be322f498d846e9a82940a7390 (opens in a new tab)
- git.kernel.org/stable/c/5315c7bacfe274ddfe649d9556e9a341ffa812da (opens in a new tab)
- git.kernel.org/stable/c/492e9cfa12f35f7946ea1b78a19f1f9337d62248 (opens in a new tab)
- git.kernel.org/stable/c/aff09d9e37e02dc60bde79035ac15b136d602259 (opens in a new tab)
- git.kernel.org/stable/c/a867abcfa85ab487066c3d3008a1ba905da04113 (opens in a new tab)
- git.kernel.org/stable/c/391517da7fd54ae40e4a7fe1cc696217343b0061 (opens in a new tab)