CVE-2026-98104: Software Security Vulnerability Vulnerability

UNKNOWN

Advisory Identifier: GHSA-5hrc-2j7x-qhwq

Published 2026-09-25

Advisory Summary

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

CVE Identifier CVE-2026-98104

GHSA Identifier GHSA-5hrc-2j7x-qhwq

Severity N/A

CVSS v3.1 Base Score N/A

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-09-25

Last Updated 2026-10-03

How to Fix CVE-2026-98104

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-98104, 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: net/sched: cls_u32: fix duplicate handle when node ID pool is exhausted gen_new_kid() falls back to returning max (htid | 0xFFF) when both idr_alloc_u32() ranges are full, instead of reporting an error. u32_change() trusts that value and inserts a new knode with a handle that is already live in the hash table, breaking handle uniqueness within the table's node ID space. The handle was never reserved in ht->handle_idr, so every later error path that does idr_remove(&ht->handle_idr, handle) removes the reservation of a different, live knode, which is then reused — one failed add compounds into further duplicates. The 4095 limit is per (table, bucket) — ht->handle_idr is per hash table and the range is derived from htid (bucketid), so a table with divisor 256 can legitimately hold 256*4095 knodes. The sibling helper gen_new_htid() has the same silent in-band failure: it returns 0 when the tp_c handle pool (1..0x7FF) is full, and u32_init() publishes the root hash table with handle 0 without checking. Two root tables with handle 0 alias in u32_lookup_ht(), allowing cross-tcf_proto knode add/lookup/delete. Add the same exhaustion check that the divisor path already has. Return an error so u32_change() fails with ENOSPC/ENOMEM when the node ID space is exhausted, and so u32_init() fails with -ENOMEM when the hash table ID space is exhausted. The extack message distinguishes pool exhaustion (-ENOSPC) from a transient allocation failure (-ENOMEM). Conditions to recreate the bug: - CONFIG_NET_SCHED=y, CONFIG_CLS_U32=y (or =m with module loaded) - Create a clsact qdisc on a device, then add 4095 u32 filters with auto-generated handles to fill the node ID space for the root hash table (single bucket). The 4096th auto-handle filter add triggers the duplicate handle (fh 800::fff reused). Reachable at Level 2 (unshare -Urn, namespace-local CAP_NET_ADMIN). - For gen_new_htid: create 2047 u32 proto entries on the same block to fill the tp_c handle pool, then create one more. The root table gets handle 0 and aliases with other handle-0 root tables.

References

NVD — CVE-2026-98104 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-98104

git.kernel.org/stable/c/6890e28840... WEB

https://git.kernel.org/stable/c/6890e28840bae4f6805e8de981c4ec8e12a4e064

git.kernel.org/stable/c/84223baf21... WEB

https://git.kernel.org/stable/c/84223baf21bc9b008444ae9bc38d5fb91fe00b9d

git.kernel.org/stable/c/d7e7e98d23... WEB

https://git.kernel.org/stable/c/d7e7e98d23f42a92d9ab7e36302bd96bd9b33b5f

git.kernel.org/stable/c/f4ee13ed7f... WEB

https://git.kernel.org/stable/c/f4ee13ed7f7b22dcd8287fcf477ae37bd84567da

git.kernel.org/stable/c/f594f04268... WEB

https://git.kernel.org/stable/c/f594f04268d01c5fdc975f3f51fc219ea2159ac6

git.kernel.org/stable/c/feab9261b5... WEB

https://git.kernel.org/stable/c/feab9261b537df4ebb8350e4779bc185373059fd

Frequently Asked Questions

What is CVE-2026-98104?

CVE-2026-98104 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-98104?

Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.

What CWE is associated with CVE-2026-98104?

CVE-2026-98104 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2026-98104?

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-5hrc-2j7x-qhwq",
  "modified" : "2026-10-03T12:31:27Z",
  "published" : "2026-09-25T12:31:36Z",
  "aliases" : [ "CVE-2026-98104" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_u32: fix duplicate handle when node ID pool is exhausted\n\ngen_new_kid() falls back to returning max (htid | 0xFFF) when both\nidr_alloc_u32() ranges are full, instead of reporting an error.\nu32_change() trusts that value and inserts a new knode with a handle\nthat is already live in the hash table, breaking handle uniqueness\nwithin the table's node ID space.\n\nThe handle was never reserved in ht->handle_idr, so every later error\npath that does idr_remove(&ht->handle_idr, handle) removes the\nreservation of a different, live knode, which is then reused — one\nfailed add compounds into further duplicates.\n\nThe 4095 limit is per (table, bucket) — ht->handle_idr is per hash\ntable and the range is derived from htid (bucketid), so a table with\ndivisor 256 can legitimately hold 256*4095 knodes.\n\nThe sibling helper gen_new_htid() has the same silent in-band failure:\nit returns 0 when the tp_c handle pool (1..0x7FF) is full, and\nu32_init() publishes the root hash table with handle 0 without\nchecking.  Two root tables with handle 0 alias in u32_lookup_ht(),\nallowing cross-tcf_proto knode add/lookup/delete.  Add the same\nexhaustion check that the divisor path already has.\n\nReturn an error so u32_change() fails with ENOSPC/ENOMEM when the\nnode ID space is exhausted, and so u32_init() fails with -ENOMEM\nwhen the hash table ID space is exhausted.  The extack message\ndistinguishes pool exhaustion (-ENOSPC) from a transient allocation\nfailure (-ENOMEM).\n\nConditions to recreate the bug:\n- CONFIG_NET_SCHED=y, CONFIG_CLS_U32=y (or =m with module loaded)\n- Create a clsact qdisc on a device, then add 4095 u32 filters with\n  auto-generated handles to fill the node ID space for the root hash\n  table (single bucket). The 4096th auto-handle filter add triggers\n  the duplicate handle (fh 800::fff reused). Reachable at Level 2\n  (unshare -Urn, namespace-local CAP_NET_ADMIN).\n- For gen_new_htid: create 2047 u32 proto entries on the same block\n  to fill the tp_c handle pool, then create one more. The root table\n  gets handle 0 and aliases with other handle-0 root tables.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98104"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6890e28840bae4f6805e8de981c4ec8e12a4e064"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/84223baf21bc9b008444ae9bc38d5fb91fe00b9d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d7e7e98d23f42a92d9ab7e36302bd96bd9b33b5f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f4ee13ed7f7b22dcd8287fcf477ae37bd84567da"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f594f04268d01c5fdc975f3f51fc219ea2159ac6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/feab9261b537df4ebb8350e4779bc185373059fd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:40Z"
  }
}

Advisory Metadata

Source ID: GHSA-5hrc-2j7x-qhwq
Schema Version: 1.4.0
Published: 2026-09-25 12:31
Last Modified: 2026-10-03 12:31
Database Record File: advisories/unreviewed/2026/09/GHSA-5hrc-2j7x-qhwq/GHSA-5hrc-2j7x-qhwq.json