CVE-2026-90058: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-59qr-qww5-6w4f
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90058
GHSA Identifier GHSA-59qr-qww5-6w4f
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-90058

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-90058, 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: bound qdisc_pkt_len to prevent qdisc soft lockup qdisc_get_stab() accepts a user-supplied size table, and __qdisc_calculate_pkt_len() amplifies qdisc_pkt_len() through the overhead, the size-table data (u16), and size_log (up to STAB_SIZE_LOG_MAX). A crafted stab can therefore set qdisc_pkt_len() to ~1 GiB for an ordinary skb. Per-flow deficit schedulers such as DRR and ETS replenish one quantum per loop iteration; with a tiny quantum (1) they spin billions of times under the qdisc lock, producing a soft lockup / RCU stall as illustrated by vega@nebusec.ai. Cap the final qdisc_pkt_len() to QDISC_PKT_LEN_MAX so the size-table amplification cannot drive deficit schedulers into an unbounded loop. A legitimate size table (e.g. qfq's overhead 999999999, which is handled by dropping) is still accepted. Introduce cap QDISC_PKT_LEN_MAX (1 << 20) = 1 MiB which is well above any legitimate single-skb wire length: the largest current skb->len is GSO_MAX_SIZE (524280), and an ATM-style size table (53/48 cell tax) amplifies that to ~578 KB, both comfortably below 1 MiB. At the same time, 1 MiB bounds the deficit refill loop to ~1M iterations per packet with quantum=1, which completes in a few milliseconds well under the demonstrated softlockup threshold (~10^9 iterations). Conditions to recreate the bug: - CONFIG_NET_SCHED=y, CONFIG_NET_SCH_DRR=y (or CONFIG_NET_SCH_ETS=y). - Attach a DRR (or ETS) root qdisc with a crafted TCA_STAB that amplifies qdisc_pkt_len to ~1 GiB (e.g. size_log=15, data=[32768]). - Add a class with a tiny quantum of 1 and send one small packet; the deficit loop spins billions of times under the qdisc lock and trips the softlockup detector (panic with kernel.softlockup_panic=1). - Reachable as root or from an unprivileged user in a fresh user+net namespace (unshare -Urn) with namespace-local CAP_NET_ADMIN.

References

NVD — CVE-2026-90058 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90058
git.kernel.org/stable/c/0bc5a6280a... WEB
https://git.kernel.org/stable/c/0bc5a6280a132a2170c6fa742436e01b635f02de
git.kernel.org/stable/c/16d21a27df... WEB
https://git.kernel.org/stable/c/16d21a27df3f50b7251c9388fc5a7ab22703b469
git.kernel.org/stable/c/1a5c26e586... WEB
https://git.kernel.org/stable/c/1a5c26e586481bc82abc19ac92c3d9f10518f525
git.kernel.org/stable/c/448c34421b... WEB
https://git.kernel.org/stable/c/448c34421b38ec7c93a0060a885218ca319d382b
git.kernel.org/stable/c/4f0f4b09a9... WEB
https://git.kernel.org/stable/c/4f0f4b09a95ef602fbdae948326beadd9c20eab3
git.kernel.org/stable/c/6e78792d8c... WEB
https://git.kernel.org/stable/c/6e78792d8ce1fa3561713860ee8086901dde4f99
git.kernel.org/stable/c/82fdbf49b9... WEB
https://git.kernel.org/stable/c/82fdbf49b9f7528c82bf608cfa9710e5f81a198c
git.kernel.org/stable/c/8f735d6438... WEB
https://git.kernel.org/stable/c/8f735d64382dcf162f4276d6699d03ad2f859c0b

Frequently Asked Questions

What is CVE-2026-90058?
CVE-2026-90058 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-90058?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90058?
CVE-2026-90058 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90058?
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-59qr-qww5-6w4f",
  "modified" : "2026-09-17T18:31:49Z",
  "published" : "2026-09-17T18:31:49Z",
  "aliases" : [ "CVE-2026-90058" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: bound qdisc_pkt_len to prevent qdisc soft lockup\n\nqdisc_get_stab() accepts a user-supplied size table, and\n__qdisc_calculate_pkt_len() amplifies qdisc_pkt_len() through the\noverhead, the size-table data (u16), and size_log (up to\nSTAB_SIZE_LOG_MAX). A crafted stab can therefore set qdisc_pkt_len()\nto ~1 GiB for an ordinary skb. Per-flow deficit schedulers such as\nDRR and ETS replenish one quantum per loop iteration; with a tiny\nquantum (1) they spin billions of times under the qdisc lock,\nproducing a soft lockup / RCU stall as illustrated by vega@nebusec.ai.\n\nCap the final qdisc_pkt_len() to QDISC_PKT_LEN_MAX so the size-table\namplification cannot drive deficit schedulers into an unbounded loop.\nA legitimate size table (e.g. qfq's overhead 999999999, which is\nhandled by dropping) is still accepted.\n\nIntroduce cap QDISC_PKT_LEN_MAX (1 << 20) = 1 MiB which is well above\nany legitimate single-skb wire length: the largest current skb->len\nis GSO_MAX_SIZE (524280), and an ATM-style size table (53/48 cell tax)\namplifies that to ~578 KB, both comfortably below 1 MiB. At the same\ntime, 1 MiB bounds the deficit refill loop to ~1M iterations per\npacket with quantum=1, which completes in a few milliseconds well\nunder the demonstrated softlockup threshold (~10^9 iterations).\n\nConditions to recreate the bug:\n- CONFIG_NET_SCHED=y, CONFIG_NET_SCH_DRR=y (or CONFIG_NET_SCH_ETS=y).\n- Attach a DRR (or ETS) root qdisc with a crafted TCA_STAB that\n  amplifies qdisc_pkt_len to ~1 GiB (e.g. size_log=15, data=[32768]).\n- Add a class with a tiny quantum of 1 and send one small packet; the\n  deficit loop spins billions of times under the qdisc lock and trips\n  the softlockup detector (panic with kernel.softlockup_panic=1).\n- Reachable as root or from an unprivileged user in a fresh user+net\n  namespace (unshare -Urn) with namespace-local CAP_NET_ADMIN.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90058"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0bc5a6280a132a2170c6fa742436e01b635f02de"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/16d21a27df3f50b7251c9388fc5a7ab22703b469"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1a5c26e586481bc82abc19ac92c3d9f10518f525"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/448c34421b38ec7c93a0060a885218ca319d382b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4f0f4b09a95ef602fbdae948326beadd9c20eab3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6e78792d8ce1fa3561713860ee8086901dde4f99"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/82fdbf49b9f7528c82bf608cfa9710e5f81a198c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8f735d64382dcf162f4276d6699d03ad2f859c0b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:16:54Z"
  }
}