CVE-2026-98022: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-vfx5-qp78-q7gw
Published
Advisory Summary

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

CVE Identifier CVE-2026-98022
GHSA Identifier GHSA-vfx5-qp78-q7gw
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-98022

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-98022, 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: cap tx_queue_len at S16_MAX to prevent oversized ring allocations Several subsystems allocate ring buffers sized by dev->tx_queue_len with no upper bound. An unprivileged user (via unshare -Urn) can set a huge tx_queue_len and exhaust global memory with ring allocations: - pfifo_fast: pfifo_fast_init() and pfifo_fast_change_tx_queue_len() allocate 3 skb_array rings of tx_queue_len entries each. - tun: tun_queue_resize() and the queue-attach path resize ptr_rings to tx_queue_len on the NETDEV_CHANGE_TX_QUEUE_LEN notifier. - tap (macvtap/ipvtap): tap_queue_resize() and tap_init() resize/init ptr_rings to tx_queue_len on the same notifier. netif_change_tx_queue_len() is the single entry point for IFLA_TXQLEN, sysfs, and the SIOCSIFTXQLEN ioctl. Cap new_len at S16_MAX (32767) there so the oversized value is rejected at set time. This takes effect whether the device is up or down, before dev->tx_queue_len is written, before any notifier fires, and before any ring is allocated. The "> S16_MAX" check also subsumes the previous unsigned-long truncation test, and a negative ifr_qlen from the ioctl lands far above the cap after conversion, so both old failure modes are covered by the one comparison. tx_queue_len is ambigious: both a per-ring sizing multiplier and a default queue-length/limit knob for consumers that allocate nothing at set time (pfifo/bfifo/gred/plug/sfb limits, htb direct_qlen, qfq max_classes, teql). 32767 is chosen as the largest value NLA_POLICY_FULL_RANGE can express for the u32 IFLA_TXQLEN policy in patch 2/3 while staying a legitimate queue length on high-BDP paths; the ring-memory trade-off of a shared knob is disclosed below. Conditions to recreate the bug: - CONFIG_NET_SCHED=y, CONFIG_VETH=y, CONFIG_USER_NS=y, CONFIG_NET_NS=y. - Unprivileged user in a fresh user+net namespace (unshare -Urn). - pfifo_fast: create veth pairs, set tx_queue_len to 500000, attach mq+pfifo_fast. ~28 iterations OOMs a 2GB guest. - tun: create 50 tun devices with IFF_MULTI_QUEUE, set tx_queue_len to 500000, open 8 queues each. ~1.6GB of ptr_ring allocations OOMs a 512MB guest. - tap: same as tun with IFF_TAP. ~960MB OOMs a 512MB guest. - On the fixed kernel the oversized tx_queue_len is rejected with -ERANGE at set time (all four paths: RTM_SETLINK, RTM_NEWLINK create, sysfs, ioctl - the latter two via this check, the former two via this check and the 2/3 parse policy respectively).

References

Frequently Asked Questions

What is CVE-2026-98022?
CVE-2026-98022 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-98022?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98022?
CVE-2026-98022 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98022?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vfx5-qp78-q7gw",
  "modified" : "2026-10-03T12:31:24Z",
  "published" : "2026-09-25T12:31:33Z",
  "aliases" : [ "CVE-2026-98022" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: cap tx_queue_len at S16_MAX to prevent oversized ring allocations\n\nSeveral subsystems allocate ring buffers sized by dev->tx_queue_len\nwith no upper bound. An unprivileged user (via unshare -Urn) can set a\nhuge tx_queue_len and exhaust global memory with ring allocations:\n\n- pfifo_fast: pfifo_fast_init() and pfifo_fast_change_tx_queue_len()\n  allocate 3 skb_array rings of tx_queue_len entries each.\n- tun: tun_queue_resize() and the queue-attach path resize ptr_rings\n  to tx_queue_len on the NETDEV_CHANGE_TX_QUEUE_LEN notifier.\n- tap (macvtap/ipvtap): tap_queue_resize() and tap_init() resize/init\n  ptr_rings to tx_queue_len on the same notifier.\n\nnetif_change_tx_queue_len() is the single entry point for IFLA_TXQLEN,\nsysfs, and the SIOCSIFTXQLEN ioctl. Cap new_len at S16_MAX (32767)\nthere so the oversized value is rejected at set time. This takes\neffect whether the device is up or down, before dev->tx_queue_len is\nwritten, before any notifier fires, and before any ring is allocated.\nThe \"> S16_MAX\" check also subsumes the previous unsigned-long\ntruncation test, and a negative ifr_qlen from the ioctl lands far\nabove the cap after conversion, so both old failure modes are covered\nby the one comparison.\n\ntx_queue_len is ambigious: both a per-ring sizing multiplier and a\ndefault queue-length/limit knob for consumers that allocate\nnothing at set time (pfifo/bfifo/gred/plug/sfb limits, htb\ndirect_qlen, qfq max_classes, teql). 32767 is chosen as the largest\nvalue NLA_POLICY_FULL_RANGE can express for the u32 IFLA_TXQLEN\npolicy in patch 2/3 while staying a legitimate queue length on\nhigh-BDP paths; the ring-memory trade-off of a shared knob is\ndisclosed below.\n\nConditions to recreate the bug:\n- CONFIG_NET_SCHED=y, CONFIG_VETH=y, CONFIG_USER_NS=y, CONFIG_NET_NS=y.\n- Unprivileged user in a fresh user+net namespace (unshare -Urn).\n- pfifo_fast: create veth pairs, set tx_queue_len to 500000, attach\n  mq+pfifo_fast. ~28 iterations OOMs a 2GB guest.\n- tun: create 50 tun devices with IFF_MULTI_QUEUE, set tx_queue_len to\n  500000, open 8 queues each. ~1.6GB of ptr_ring allocations OOMs a\n  512MB guest.\n- tap: same as tun with IFF_TAP. ~960MB OOMs a 512MB guest.\n- On the fixed kernel the oversized tx_queue_len is rejected with\n  -ERANGE at set time (all four paths: RTM_SETLINK, RTM_NEWLINK\n  create, sysfs, ioctl - the latter two via this check, the former\n  two via this check and the 2/3 parse policy respectively).",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98022"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/081340cf70a789b94b4174af54a63ffd49677a4e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/24d02c909a1725ab9eceb92db7d02e4e841f17ca"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5e5591a0f33f7c11bf1d338dbb6c5072575de64c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/66ab4c59b74db7ab53a1c9083feaaede393a96a0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/81c0e02076989743a603806a5a4f44d2c40dc01f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a03b927bae4af5c23fd5315a237855c17cc8f422"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c2362c500931e5bd1826bce34e9ce28af80e7541"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c8d4060610c69645733c92d94fceb4b93808ac4d"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:30Z"
  }
}