{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89518 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89518 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-89518 and fix it if it is affected.\n\nWhat it is: CVE-2026-89518 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-89518 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-89518/ (Markdown: https://insights.sbomify.com/CVE-2026-89518/index.md)","id":"CVE-2026-89518","markdown":"https://insights.sbomify.com/CVE-2026-89518/index.md","name":"CVE-2026-89518","record":{"aliases":["DEBIAN-CVE-2026-89518","GHSA-45rw-88gp-h7jx","UBUNTU-CVE-2026-89518"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel's sched_ext subsystem can cause deadlocks during core scheduling, leading to 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: Fix this_rq() assumptions in dispatch kfuncs\n\nUnder core scheduling, dispatch runs from within the core-wide pick and can\ntarget a sibling rq, so ops.dispatch() may execute on a CPU different from\nthe dispatched rq's. Several kfunc paths assumed the two always coincide:\n\n- scx_dsq_move() decided whether an rq lock is held by testing this_rq()'s\n  rq flags and lock-danced accordingly. A dispatch for a sibling took the\n  unlocked-context branch and acquired the source rq lock on top of the\n  already held dispatched rq lock which could deadlock.\n\n- scx_bpf_sub_dispatch() dispatched this_rq() with its stashed\n  sub_dispatch_prev, which is NULL when dispatching for a sibling.\n\n- finish_dispatch(), scx_bpf_dsq_reenq() and scx_bpf_dsq_nr_queued()\n  resolved SCX_DSQ_LOCAL to this CPU's local DSQ rather than the dispatched\n  rq's. The latter two are callable from other rq-locked operations too,\n  where SCX_DSQ_LOCAL now likewise resolves to the op's rq. This changes\n  behavior also without core scheduling, e.g. for ops.enqueue() running a\n  remote wakeup on the waking CPU, and is intended: which CPU happens to\n  execute an operation is incidental, the op's rq is what it is operating\n  on, and the resolution now matches the insert side where SCX_DSQ_LOCAL\n  dispatches land on the task's rq.\n\nUse the rq tracked by scx_locked_rq(), which is set to the dispatched rq\naround ops invocations and NULL in unlocked contexts.","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 this_rq() assumptions in dispatch kfuncs","id":"CVE-2026-89518","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_ext: Replace SCX_RQ_BAL_KEEP with a dispatch verdict return","id":"CVE-2026-89519"},"packages":[],"prev":{"headline":"sched_ext: Fix rq-\u003ecore_pick corruption under core scheduling","id":"CVE-2026-89517"},"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 subsystem can cause deadlocks during core scheduling, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-89518/"}