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]
Fix
Microsoft's update · Moderate
- Release Notes — azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 · build 6.6.159.1-1
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-29.
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 2
- StatusReceived → PublishedNVD modified 2026-10-19 09:22
- First seenunscoredNVD modified 2026-10-19 10:19
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 8
- https://git.kernel.org/stable/c/0d096a7f7d79207490858dde731b16da5337e90c
- https://git.kernel.org/stable/c/391517da7fd54ae40e4a7fe1cc696217343b0061
- https://git.kernel.org/stable/c/492e9cfa12f35f7946ea1b78a19f1f9337d62248
- https://git.kernel.org/stable/c/5315c7bacfe274ddfe649d9556e9a341ffa812da
- https://git.kernel.org/stable/c/9d550924961f61a491dd95359c63494fa8a23d9f
- https://git.kernel.org/stable/c/a867abcfa85ab487066c3d3008a1ba905da04113
- https://git.kernel.org/stable/c/aff09d9e37e02dc60bde79035ac15b136d602259
- https://git.kernel.org/stable/c/db5dd9f47b4df1be322f498d846e9a82940a7390