{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98864 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98864 is a 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-98864 and fix it if it is affected.\n\nWhat it is: CVE-2026-98864 is a 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-98864 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-98864/ (Markdown: https://insights.sbomify.com/CVE-2026-98864/index.md)","id":"CVE-2026-98864","markdown":"https://insights.sbomify.com/CVE-2026-98864/index.md","name":"CVE-2026-98864","record":{"aliases":["DEBIAN-CVE-2026-98864","GHSA-fpjr-j5w9-j6gm","UBUNTU-CVE-2026-98864"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel scheduler","requires_auth":"none","summary":"A race condition in the Linux kernel scheduler allows tasks to be dropped during reenqueueing, potentially causing 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: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task\n\nebf1ccff79c4 (\"sched_ext: Fix ops.dequeue() semantics\") moved the final\nops_state store in scx_dispatch_enqueue() after the DSQ unlock so that the\ncustody update and ops.dequeue() precede it. A task can thus be found on a\nDSQ while still SCX_OPSS_DISPATCHING.\n\nThe dequeue and core-sched pick paths wait for the state to clear in\nops_dequeue() but the reenqueue paths don't. A reenqueue in that window runs\nops.enqueue() and sets SCX_OPSS_QUEUED before the dispatch has completed.\nThe dispatcher's final store then overwrites it with SCX_OPSS_NONE and\nfinish_dispatch() drops every later dispatch of the task.\n\nWait for SCX_OPSS_DISPATCHING to clear before dequeueing a task for\nreenqueue, the same way ops_dequeue() does.","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: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task","id":"CVE-2026-98864","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: Don't run ops.dequeue() with a DSQ lock held","id":"CVE-2026-98865"},"packages":[],"prev":{"headline":"KVM: x86: Re-pend GET_NESTED_STATE_PAGES if getting said pages fails","id":"CVE-2026-98863"},"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 race condition in the Linux kernel scheduler allows tasks to be dropped during reenqueueing, potentially causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-98864/"}