{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89519 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89519 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-89519 and fix it if it is affected.\n\nWhat it is: CVE-2026-89519 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-89519 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-89519/ (Markdown: https://insights.sbomify.com/CVE-2026-89519/index.md)","id":"CVE-2026-89519","markdown":"https://insights.sbomify.com/CVE-2026-89519/index.md","name":"CVE-2026-89519","record":{"aliases":["DEBIAN-CVE-2026-89519","GHSA-4vmj-w324-pvrj","UBUNTU-CVE-2026-89519"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel's sched_ext scheduler can cause a stale flag to keep a dequeued task running, potentially leading to system instability or denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return\n\nSCX_RQ_BAL_KEEP tells the pick to keep running the previous task, a leftover\nfrom when balancing and picking were separate operations. An rq-level flag\nonly works while dispatches and picks pair up one to one, which core\nscheduling breaks: selections interleave through dispatch's lock drops and a\npick can consume a stale flag, keeping a task that has since been dequeued.\nFixing core scheduling support requires the decision to travel with the\ndispatch that made it. Make scx_dispatch_sched() and balance_one() return an\nexplicit verdict instead and drop the flag's plumbing from the tools autogen\nenum headers.\n\nAlso factor the pick-side invocation, its follow-up queueing and the\npost-dispatch checks out of do_pick_task_scx() into dispatch_pick(). No\nfunctional changes intended.\n\nv2: Drop the SCX_RQ_BAL_KEEP plumbing from the tools autogen enum headers\n    as well (Andrea).","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: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return","id":"CVE-2026-89519","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"sched/core: Make core-sched flips wait for in-flight selections","id":"CVE-2026-89520"},"packages":[],"prev":{"headline":"sched_ext: Fix this_rq() assumptions in dispatch kfuncs","id":"CVE-2026-89518"},"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 sched_ext scheduler can cause a stale flag to keep a dequeued task running, potentially leading to system instability or denial of service.","url":"https://insights.sbomify.com/CVE-2026-89519/"}