{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98623 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98623 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98623 and fix it if it is affected.\n\nWhat it is: CVE-2026-98623 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98623 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98623/ (Markdown: https://insights.sbomify.com/CVE-2026-98623/index.md)","id":"CVE-2026-98623","markdown":"https://insights.sbomify.com/CVE-2026-98623/index.md","name":"CVE-2026-98623","record":{"aliases":["AZL-108626","BELL-CVE-2026-98623","DEBIAN-CVE-2026-98623","GHSA-5c9q-m24x-7r34","UBUNTU-CVE-2026-98623"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker with debugfs access can trigger an out-of-bounds read in the nouveau driver, potentially causing a kernel crash or information disclosure.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update\n\nIf list_for_each_entry() exits without hitting a break then \"pstate\" is\nnot a valid pstate pointer.  Introduce a \"found\" variable instead.\n\nThe check is reachable from userspace: nvkm_clk_ustate_update() takes the\npstate id straight from the 'pstate' debugfs file, so requesting an id\nthat is not in clk-\u003estates - or any id at all when the perf tables are\nbroken and the list is empty - makes the pstate-\u003epstate != req test\ndereference the list head cast to a struct nvkm_pstate, which is an\nout-of-bounds read.\n\n[Francesco: rebased on drm-misc-next, expanded the commit message]","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update","id":"CVE-2026-98623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"netfilter: nfnetlink_queue: hold nfnl mutex in event notifier","id":"CVE-2026-98624"},"packages":[],"prev":{"headline":"net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure","id":"CVE-2026-98622"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker with debugfs access can trigger an out-of-bounds read in the nouveau driver, potentially causing a kernel crash or information disclosure.","url":"https://insights.sbomify.com/CVE-2026-98623/"}