{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89517 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89517 is a vulnerability in Linux, published on 11 Sep 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-89517 and fix it if it is affected.\n\nWhat it is: CVE-2026-89517 is a vulnerability in Linux, published on 11 Sep 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-89517 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-89517/ (Markdown: https://insights.sbomify.com/CVE-2026-89517/index.md)","id":"CVE-2026-89517","markdown":"https://insights.sbomify.com/CVE-2026-89517/index.md","name":"CVE-2026-89517","record":{"aliases":["DEBIAN-CVE-2026-89517","GHSA-xg94-9m82-xc6c","UBUNTU-CVE-2026-89517"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel scheduler","requires_auth":"none","summary":"A race condition in the Linux kernel's core scheduling can cause a NULL pointer dereference and system hang, requiring local access and specific SMT hardware.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nsched_ext: Fix rq-\u003ecore_pick corruption under core scheduling\n\nCore scheduling's pick_next_task() picks what to run on every SMT sibling of\nthe core in a single pass under the shared core-wide rq lock. The selection\nstate is consistent only while the lock is held continuously, so\n-\u003epick_task() originally could not release it. However, since 4c95380701f5\n(\"sched/ext: Fold balance_scx() into pick_task_scx()\"), sched_ext runs\ndispatch from inside the pick and dispatching can drop the rq lock. To\nsupport this, pick_next_task() has been updated to restart the whole\nselection when a pick returns RETRY_TASK after releasing the lock.\n\nWhen selections on the same core interleave through the dropped lock, they\ncorrupt each other's state: one clears the other's rq-\u003ecore_pick leading to\na NULL deref, or invalidates its keep-the-previous-task decision leaving a\ndequeued task running, which deadlocks the next wakeup and matches the\nreported hard hangs. A cookied ping-pong load on an SMT machine makes the\ninterleavings frequent and kills the kernel within seconds.\n\nFix it by making the pick return RETRY_TASK whenever dispatch released the\nrq lock, so that a selection only ever commits picks made under a\ncontinuously held lock. The previous patch's rq-\u003escx.lock_drop_seq counts\nthe releases. A dispatch that touched nothing never releases the lock and\nits verdict, including \"nothing to run\", stands: retries are bounded, each\nfollowing a dispatch that actually did something, and an idle CPU does not\nloop.\n\nIf another dispatch is already in flight on the rq, skip dispatching and\npick from what is already queued locally - the in-flight dispatch has\nreleased the lock, so its own selection will retry and re-pick this rq,\nwhile returning RETRY_TASK here would only spin on the lock that dispatch\nneeds to finish.\n\nBalance callbacks must run in the context that queued them, so they can only\nbe queued on the CPU's own rq. When dispatching for another rq, run the\ndeferred work directly instead - that rq may consume all its picks through\nthe core-sched fast path and never queue the callback itself.\n\nThe put_prev_task_scx() warning about a runnable task being left behind\nassumed that dispatch ran as part of the very pick that is switching away.\nThat now only holds on the non-core path, so gate it and drop the\ncookie-match test, which is always true without core scheduling, from its\ncondition.","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":"sched_ext: Fix rq-\u003ecore_pick corruption under core scheduling","id":"CVE-2026-89517","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"sched_ext: Fix this_rq() assumptions in dispatch kfuncs","id":"CVE-2026-89518"},"packages":[],"prev":{"headline":"sched_ext: Don't BUG_ON a destroyed DSQ in process_deferred_reenq_users","id":"CVE-2026-89516"},"products":["Linux"],"published":"2026-09-11","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 race condition in the Linux kernel's core scheduling can cause a NULL pointer dereference and system hang, requiring local access and specific SMT hardware.","url":"https://insights.sbomify.com/CVE-2026-89517/"}