Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98623drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update

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]

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 7c856522069755ab9d163a24ac332cd3cb35fe30 – < db5dd9f47b4df1be322f498d846e9a82940a7390
    • affected 7c856522069755ab9d163a24ac332cd3cb35fe30 – < 9d550924961f61a491dd95359c63494fa8a23d9f
    • affected 7c856522069755ab9d163a24ac332cd3cb35fe30 – < 492e9cfa12f35f7946ea1b78a19f1f9337d62248
    • affected 7c856522069755ab9d163a24ac332cd3cb35fe30 – < a867abcfa85ab487066c3d3008a1ba905da04113
    • affected 7c856522069755ab9d163a24ac332cd3cb35fe30 – < 5315c7bacfe274ddfe649d9556e9a341ffa812da
    • affected 7c856522069755ab9d163a24ac332cd3cb35fe30 – < 0d096a7f7d79207490858dde731b16da5337e90c
    • affected 7c856522069755ab9d163a24ac332cd3cb35fe30 – < 391517da7fd54ae40e4a7fe1cc696217343b0061
    • affected 7c856522069755ab9d163a24ac332cd3cb35fe30 – < aff09d9e37e02dc60bde79035ac15b136d602259
  • Linux · Linux

    • affected 3.13
    • unaffected < 3.13
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98623 badge
[![CVE-2026-98623](https://cveledger.app/badge/CVE-2026-98623.svg)](https://cveledger.app/cve/CVE-2026-98623)

Record last updated .