CVE-2026-98832: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98832 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-98832 at a Glance
How to Fix CVE-2026-98832
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-98832, 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-98832?
Which Software versions are affected?
What version fixes CVE-2026-98832?
What CWE is associated with CVE-2026-98832?
How can I check Maven dependencies for CVE-2026-98832?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9gxg-wj69-fwm2",
"modified" : "2026-10-18T18:32:05Z",
"published" : "2026-10-18T18:32:05Z",
"aliases" : [ "CVE-2026-98832" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-cgroup: save IRQ state in blkg_tryget_closest()\n\nbio_set_dev() associates the bio with a blkg through bio_associate_blkg().\nIf the blkg lookup misses, blkg_tryget_closest() takes q->queue_lock with\nspin_lock_irq() and releases it with spin_unlock_irq(), which\nunconditionally enables local interrupts.\n\nCallers may call bio_set_dev() with interrupts already disabled, e.g.\ndm-thin's pool_map() does so while holding pool->lock taken with\nspin_lock_irq(). The nested spin_unlock_irq() then enables interrupts\nwhile pool->lock is still held, so an I/O completion softirq can run on\nthe same CPU, re-acquire pool->lock (thin_endio(), or overwrite_endio()\n-> complete_mapping_preparation()) and deadlock. lockdep reports this\nas inconsistent SOFTIRQ-ON-W to IN-SOFTIRQ-W usage.\n\nCommit 3a762de55b4e (\"block: save irq state in blkg_lookup_create()\")\nfixed the same problem while the lock lived in blkg_lookup_create(), but\ncommit 9327a865e395 (\"blk-cgroup: don't nest queue_lock under rcu in\nblkg_lookup_create()\") moved the locking into blkg_tryget_closest() and\nreverted it to spin_lock_irq().\n\nSave and restore the caller's IRQ state instead.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98832"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/327c428ba79b13e4cc5253333a9d5c0aa5579bdf"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9fcf4317384ce6758c3127a6e8914c54cbb9c8cc"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:37Z"
}
}