CVE-2026-98219: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98219 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-98219 at a Glance
How to Fix CVE-2026-98219
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-98219, 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-98219?
Which Software versions are affected?
What version fixes CVE-2026-98219?
What CWE is associated with CVE-2026-98219?
How can I check Maven dependencies for CVE-2026-98219?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-fmhg-ffq7-4rm5",
"modified" : "2026-10-06T09:31:31Z",
"published" : "2026-10-06T09:31:31Z",
"aliases" : [ "CVE-2026-98219" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Close the pre-enable ops error claim window\n\nscx_alloc_and_add_sched() publishes ops->priv before\nscx_root_enable_workfn() switches the state to SCX_ENABLING. An error\nclaimed via scx_bpf_error_bstr() from an associated BPF program in that\nwindow is consumed by scx_disable_workfn(), which takes the pre-enable\nshortcut in scx_root_disable(). The shortcut returns without any teardown\nand restores SCX_DISABLED with an unconditional scx_set_enable_state() xchg\nracing the enable workfn's own transition. The enable then completes with\nthe claim consumed: the scheduler stays up but can never be disabled again,\nand bpf_scx_unreg() frees it while still in use, resulting in a\nuse-after-free. Both WARN_ON_ONCE()s fire back to back:\n\n WARNING: kernel/sched/ext/ext.c:7522 at\n scx_root_enable_workfn+0xeec/0x1be0, CPU#3: scx_enable_help/276\n\n WARNING: kernel/sched/ext/ext.c:6398 at scx_root_disable+0xb50/0xdb8,\n CPU#0: sched_ext_helpe/664\n\nscx_root_enable_workfn() switches to SCX_ENABLING before the scheduler\nallocation, so ops->priv is never visible while SCX_DISABLED. The allocation\nfailure path restores SCX_DISABLED.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98219"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/959c66dc4a915be306c35691095c787c61dc7df9"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c7a1c6e8004ab12a9c9bfdcb603f60f9bf4a3cee"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-06T09:18:08Z"
}
}