CVE-2026-90099: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-3537-p4vp-g252
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90099
GHSA Identifier GHSA-3537-p4vp-g252
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-90099

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-90099, 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: account classifier filter allocations to memcg Allocations in the tc classifier *_change() paths (filter objects, per-CPU counters, and per-filter aux data) use plain GFP_KERNEL without __GFP_ACCOUNT, allowing unprivileged users to pin kernel memory outside memcg charging. The shared tcf_exts_init_ex() action array allocation in cls_api.c was also uncharged; this patch closes it along with the per-classifier filter-object/percpu/aux allocations that remain unaccounted. Add GFP_KERNEL_ACCOUNT to: - the shared tcf_exts_init_ex() action array (cls_api.c), common to every filter of every classifier (32 pointers, 256 bytes); - the filter-object, per-CPU-counter, and per-filter aux allocations in cls_basic, cls_bpf, cls_cgroup, cls_flow, cls_flower, cls_fw, cls_matchall, cls_route and cls_u32; - the u32_init_knode() replace-path knode allocation (cls_u32.c), which allocates the same struct tc_u_knode + sel.keys on every replace of an existing knode and was missed by the create-path-only conversion. Also fix the cls_basic error path: basic_change() inserts fnew into the IDR before allocating the per-CPU counter. If alloc_percpu() fails the errout path kfree'd fnew without idr_remove, leaving a dangling pointer in the IDR. With GFP_KERNEL_ACCOUNT the percpu alloc becomes failable on demand (memcg at memory.max), making the dead path attacker-reachable and burning the handle permanently. Add the idr_remove on the percpu failure path, matching the basic_set_parms failure-path pattern. Note: vega@nebusec.ai provided a poc for basic_cls, but it was easy to extend to the other classifiers. Conditions to recreate the bug: - CONFIG_NET_SCHED, CONFIG_NET_CLS_* (the classifier being used), CONFIG_NET_CLS_ACT, CONFIG_MEMCG, CONFIG_USER_NS, CONFIG_NET_NS. - Unprivileged user in a fresh user+network namespace (unshare -Urn), or root with CAP_NET_ADMIN. - Create a large number of tc filters (e.g. tc filter add dev lo ingress ... <classifier> ...) while watching a memcg-limited cgroup: system slab grows far faster than memory.current, pinning kernel memory outside memcg charging.

References

NVD — CVE-2026-90099 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90099
git.kernel.org/stable/c/18c68c8f3d... WEB
https://git.kernel.org/stable/c/18c68c8f3d3ff0a4def1391021b439c4333a6c71
git.kernel.org/stable/c/1beb81947e... WEB
https://git.kernel.org/stable/c/1beb81947eb486716af80db7a584f9e9fef7e003
git.kernel.org/stable/c/68fb306071... WEB
https://git.kernel.org/stable/c/68fb30607169c92de57c5c82b6af8a733af1cc09

Frequently Asked Questions

What is CVE-2026-90099?
CVE-2026-90099 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-90099?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90099?
CVE-2026-90099 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90099?
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-3537-p4vp-g252",
  "modified" : "2026-10-15T12:30:48Z",
  "published" : "2026-09-17T18:31:50Z",
  "aliases" : [ "CVE-2026-90099" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: account classifier filter allocations to memcg\n\nAllocations in the tc classifier *_change() paths (filter objects,\nper-CPU counters, and per-filter aux data) use plain GFP_KERNEL without\n__GFP_ACCOUNT, allowing unprivileged users to pin kernel memory outside\nmemcg charging. The shared tcf_exts_init_ex() action array allocation in\ncls_api.c was also uncharged; this patch closes it along with the\nper-classifier filter-object/percpu/aux allocations that remain\nunaccounted.\n\nAdd GFP_KERNEL_ACCOUNT to:\n- the shared tcf_exts_init_ex() action array (cls_api.c), common to every\n  filter of every classifier (32 pointers, 256 bytes);\n- the filter-object, per-CPU-counter, and per-filter aux allocations in\n  cls_basic, cls_bpf, cls_cgroup, cls_flow, cls_flower, cls_fw,\n  cls_matchall, cls_route and cls_u32;\n- the u32_init_knode() replace-path knode allocation (cls_u32.c), which\n  allocates the same struct tc_u_knode + sel.keys on every replace of an\n  existing knode and was missed by the create-path-only conversion.\n\nAlso fix the cls_basic error path: basic_change() inserts fnew into the\nIDR before allocating the per-CPU counter. If alloc_percpu() fails the\nerrout path kfree'd fnew without idr_remove, leaving a dangling pointer\nin the IDR. With GFP_KERNEL_ACCOUNT the percpu alloc becomes failable\non demand (memcg at memory.max), making the dead path attacker-reachable\nand burning the handle permanently. Add the idr_remove on the percpu\nfailure path, matching the basic_set_parms failure-path pattern.\n\nNote: vega@nebusec.ai provided a poc for basic_cls, but it was easy to\nextend to the other classifiers.\n\nConditions to recreate the bug:\n- CONFIG_NET_SCHED, CONFIG_NET_CLS_* (the classifier being used),\n  CONFIG_NET_CLS_ACT, CONFIG_MEMCG, CONFIG_USER_NS, CONFIG_NET_NS.\n- Unprivileged user in a fresh user+network namespace (unshare -Urn),\n  or root with CAP_NET_ADMIN.\n- Create a large number of tc filters (e.g. tc filter add dev lo\n  ingress ... <classifier> ...) while watching a memcg-limited cgroup:\n  system slab grows far faster than memory.current, pinning kernel\n  memory outside memcg charging.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90099"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/18c68c8f3d3ff0a4def1391021b439c4333a6c71"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1beb81947eb486716af80db7a584f9e9fef7e003"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/68fb30607169c92de57c5c82b6af8a733af1cc09"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:01Z"
  }
}