CVE-2026-98623: drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 0d096a7f7d79207490858dde731b16da5337e90c, 391517da7fd54ae40e4a7fe1cc696217343b0061, 492e9cfa12f35f7946ea1b78a19f1f9337d62248; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0d096a7f7d79207490858dde731b16da5337e90c, 391517da7fd54ae40e4a7fe1cc696217343b0061, 492e9cfa12f35f7946ea1b78a19f1f9337d62248; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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]
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.13affected
- 7c856522069755ab9d163a24ac332cd3cb35fe30 and later · before db5dd9f47b4df1be322f498d846e9a82940a7390affected · git
- 7c856522069755ab9d163a24ac332cd3cb35fe30 and later · before 9d550924961f61a491dd95359c63494fa8a23d9faffected · git
- 7c856522069755ab9d163a24ac332cd3cb35fe30 and later · before 492e9cfa12f35f7946ea1b78a19f1f9337d62248affected · git
- 7c856522069755ab9d163a24ac332cd3cb35fe30 and later · before a867abcfa85ab487066c3d3008a1ba905da04113affected · git
- 7c856522069755ab9d163a24ac332cd3cb35fe30 and later · before 5315c7bacfe274ddfe649d9556e9a341ffa812daaffected · git
- 7c856522069755ab9d163a24ac332cd3cb35fe30 and later · before 0d096a7f7d79207490858dde731b16da5337e90caffected · git
- 7c856522069755ab9d163a24ac332cd3cb35fe30 and later · before 391517da7fd54ae40e4a7fe1cc696217343b0061affected · git
- 7c856522069755ab9d163a24ac332cd3cb35fe30 and later · before aff09d9e37e02dc60bde79035ac15b136d602259affected · git
- before 3.13not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98621Oct 18, 2026 · net: gue: reject invalid REMCSUM offsets0Monitor
- ← EarlierCVE-2026-98622Oct 18, 2026 · net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure0Monitor
- Later →CVE-2026-98624Oct 18, 2026 · netfilter: nfnetlink_queue: hold nfnl mutex in event notifier0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0d096a7f7d79207490858dde731b16da5337e90c | Vendor (CNA) |
| Linux Linux | 391517da7fd54ae40e4a7fe1cc696217343b0061 | Vendor (CNA) |
| Linux Linux | 492e9cfa12f35f7946ea1b78a19f1f9337d62248 | Vendor (CNA) |
| Linux Linux | 5315c7bacfe274ddfe649d9556e9a341ffa812da | Vendor (CNA) |
| Linux Linux | 9d550924961f61a491dd95359c63494fa8a23d9f | Vendor (CNA) |
| Linux Linux | a867abcfa85ab487066c3d3008a1ba905da04113 | Vendor (CNA) |
| Linux Linux | aff09d9e37e02dc60bde79035ac15b136d602259 | Vendor (CNA) |
| Linux Linux | db5dd9f47b4df1be322f498d846e9a82940a7390 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/391517da7fd54ae40e4a7fe1cc696217343b0061
- git.kernel.org/stable/c/492e9cfa12f35f7946ea1b78a19f1f9337d62248
- git.kernel.org/stable/c/5315c7bacfe274ddfe649d9556e9a341ffa812da
- git.kernel.org/stable/c/9d550924961f61a491dd95359c63494fa8a23d9f
- git.kernel.org/stable/c/a867abcfa85ab487066c3d3008a1ba905da04113
- git.kernel.org/stable/c/aff09d9e37e02dc60bde79035ac15b136d602259
- git.kernel.org/stable/c/db5dd9f47b4df1be322f498d846e9a82940a7390
Vendor advisories and official records. Exploit/PoC links are deliberately left out.