CVE-2026-98598: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-3wx3-9xwg-38ff
Share
Published
Advisory Summary

CVE-2026-98598 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-98598 at a Glance

CVE Identifier CVE-2026-98598
GHSA Identifier GHSA-3wx3-9xwg-38ff
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98598

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.

Verify Direct and Transitive Dependencies

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-98598, 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

In the Linux kernel, the following vulnerability has been resolved: ipv6: Prevent rt6_insert_exception() for dying fib6_info. Before the cited commit, fib6_nh_flush_exceptions() always set from->exception_bucket_flushed = 1 under rt6_exception_lock to prevent rt6_insert_exception() from inserting a new exception for a dying fib6_info. The flag was replaced with the FIB6_EXCEPTION_BUCKET_FLUSHED bit stored in nh->rt6i_exception_bucket. The problem is that now the bit is only set when the bucket is not NULL and fib6_nh_flush_exceptions() is called from fib6_nh_release() after fib6_ref has already reached zero. If rt6_insert_exception() is called while the target fib6_info is being removed via fib6_purge_rt(), a new exception could be created successfully because rt6_flush_exceptions() no longer sets the bit. This creates a reference cycle between the fib6_info and the exception route, leaking the fib6_info, its nexthop device, and all per-CPU routes in fib6_nh->rt6i_pcpu, which stalls netdev unregistration. [ 34.680602] unregister_netdevice: waiting for gre6 to become free. Usage count = 68 [ 44.920675] unregister_netdevice: waiting for gre6 to become free. Usage count = 68 [ 55.176582] unregister_netdevice: waiting for gre6 to become free. Usage count = 68 Let's call fib6_drop_pcpu_from() before rt6_flush_exceptions(), to set fib6_destroying before rt6_exception_lock, and check f6i->fib6_destroying in rt6_insert_exception(). Note that FIB6_EXCEPTION_BUCKET_FLUSHED logic is dead and we can clean it up in net-next.

References

NVD — CVE-2026-98598 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98598
git.kernel.org/stable/c/0346ec2f08... WEB
https://git.kernel.org/stable/c/0346ec2f080b40d95ed05b853bb9226289e75212
git.kernel.org/stable/c/649ffc76ed... WEB
https://git.kernel.org/stable/c/649ffc76ed5483b2caf35ed90d3787538efc4e53
git.kernel.org/stable/c/e03e77071e... WEB
https://git.kernel.org/stable/c/e03e77071e75ce726d877f0a4349a28b6e1f487a

Frequently Asked Questions

What is CVE-2026-98598?
CVE-2026-98598 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98598?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98598?
CVE-2026-98598 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98598?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3wx3-9xwg-38ff",
  "modified" : "2026-10-18T18:31:55Z",
  "published" : "2026-10-18T18:31:55Z",
  "aliases" : [ "CVE-2026-98598" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Prevent rt6_insert_exception() for dying fib6_info.\n\nBefore the cited commit, fib6_nh_flush_exceptions() always set\nfrom->exception_bucket_flushed = 1 under rt6_exception_lock to\nprevent rt6_insert_exception() from inserting a new exception\nfor a dying fib6_info.\n\nThe flag was replaced with the FIB6_EXCEPTION_BUCKET_FLUSHED\nbit stored in nh->rt6i_exception_bucket.\n\nThe problem is that now the bit is only set when the bucket\nis not NULL and fib6_nh_flush_exceptions() is called from\nfib6_nh_release() after fib6_ref has already reached zero.\n\nIf rt6_insert_exception() is called while the target fib6_info\nis being removed via fib6_purge_rt(), a new exception could be\ncreated successfully because rt6_flush_exceptions() no longer\nsets the bit.\n\nThis creates a reference cycle between the fib6_info and the\nexception route, leaking the fib6_info, its nexthop device,\nand all per-CPU routes in fib6_nh->rt6i_pcpu, which stalls netdev\nunregistration.\n\n[   34.680602] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n[   44.920675] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n[   55.176582] unregister_netdevice: waiting for gre6 to become free. Usage count = 68\n\nLet's call fib6_drop_pcpu_from() before rt6_flush_exceptions(),\nto set fib6_destroying before rt6_exception_lock, and check\nf6i->fib6_destroying in rt6_insert_exception().\n\nNote that FIB6_EXCEPTION_BUCKET_FLUSHED logic is dead and\nwe can clean it up in net-next.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98598"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0346ec2f080b40d95ed05b853bb9226289e75212"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/649ffc76ed5483b2caf35ed90d3787538efc4e53"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e03e77071e75ce726d877f0a4349a28b6e1f487a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:12Z"
  }
}