{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99183 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99183 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99183 and fix it if it is affected.\n\nWhat it is: CVE-2026-99183 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99183 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-99183/ (Markdown: https://insights.sbomify.com/CVE-2026-99183/index.md)","id":"CVE-2026-99183","markdown":"https://insights.sbomify.com/CVE-2026-99183/index.md","name":"CVE-2026-99183","record":{"aliases":["BELL-CVE-2026-99183","DEBIAN-CVE-2026-99183","GHSA-cgc9-44mx-vhwg","UBUNTU-CVE-2026-99183"],"analysis":null,"analysis_generated_by":null,"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\naccel/rocket: search every core slot when looking up a scheduler\n\nsched_to_core() walks rdev-\u003ecores[] up to rdev-\u003enum_cores, and\nrocket_remove() decrements num_cores for every core it removes. Unbind a\ncore that is not the last one and the cores behind it fall outside the\nsearch, so sched_to_core() returns NULL for a core that is still bound and\nstill running jobs. Neither caller checks the result:\n\n  rocket_job_run():      rocket_fence_create(core), core-\u003edev\n  rocket_job_timedout(): dev_err(core-\u003edev, \"NPU job timed out\")\n\nUnbinding the middle core of the three on an RK3588 while three clients are\nsubmitting to all of them faults twice, once from the surviving core's\njob queue and once from its reset work:\n\n  KASAN: null-ptr-deref in range [0x0000000000000220-0x0000000000000227]\n  Workqueue: fdad0000.npu drm_sched_run_job_work [gpu_sched]\n  pc : rocket_job_run+0x234/0x838 [rocket]\n  Call trace:\n   rocket_job_run+0x234/0x838 [rocket]\n   drm_sched_run_job_work+0x2cc/0xad8 [gpu_sched]\n   process_one_work+0x640/0x14f0\n\n  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n  Workqueue: rocket-reset-2 drm_sched_job_timedout [gpu_sched]\n  pc : rocket_job_timedout+0xf0/0x1e0 [rocket]\n  Call trace:\n   rocket_job_timedout+0xf0/0x1e0 [rocket]\n   drm_sched_job_timedout+0x188/0x6a0 [gpu_sched]\n\nBoth are the third core: the workqueue names are its device and its\ncore-\u003eindex, and it was left at slot 2 while num_cores had dropped to 2.\n\nSearch all the slots that were allocated, the way find_core_for_dev() now\ndoes. A core that is still bound is then found, and the two callers get\nthe pointer they already assume they have.\n\nThis does not make unbinding one core out of several safe. An open client\nkeeps an entity pointing at the scheduler of the core that went away:\ndrm_sched reports it as not ready for every job that lands on it, and the\nclient waits in dma_fence_default_wait for a fence that will never signal.\nStopping the NULL dereference is what belongs in a fix; the rest wants\nmore thought.","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":"accel/rocket: search every core slot when looking up a scheduler","id":"CVE-2026-99183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"accel/rocket: search every core slot when a core is removed","id":"CVE-2026-99184"},"packages":[],"prev":{"headline":"ASoC: SOF: ipc4-topology: Fix shift-out-of-bounds for aggregated ALH capture","id":"CVE-2026-99182"},"products":["Linux"],"published":"2026-10-28","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-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99183/"}