CVE-2026-98864: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98864 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-98864 at a Glance
How to Fix CVE-2026-98864
To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-98864, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree
Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
References
Frequently Asked Questions
What is CVE-2026-98864?
Which Software versions are affected?
What version fixes CVE-2026-98864?
What CWE is associated with CVE-2026-98864?
How can I check Maven dependencies for CVE-2026-98864?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-fpjr-j5w9-j6gm",
"modified" : "2026-10-18T18:32:06Z",
"published" : "2026-10-18T18:32:06Z",
"aliases" : [ "CVE-2026-98864" ],
"details" : "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.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98864"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/43457bf6550044c40bd6d3fcdf9ea66f5a55d139"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7de9a6fb44eae4f05e68c805d58b9c618815adfa"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:40Z"
}
}