CVE-2026-90313: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-2mrf-g72x-r6vx
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90313
GHSA Identifier GHSA-2mrf-g72x-r6vx
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-90313

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-90313, 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: bpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed A potential invalid storage access issue can occur after replacing a cgroup bpf prog. This occurs in the following scenario: 1. prog1 with storage is attached to a cgroup in multi-attach mode. 2. prog1 is replaced with prog2 using BPF_F_REPLACE in multi-attach mode, but fails midway (e.g. in bpf_trampoline_link_cgroup_shim or update_effective_progs). 3. A new prog3 is attached to the cgroup in multi-attach mode. The reason is that __cgroup_bpf_attach overwrites pl->storage with the new storage prior to attachment completion. When attachment fails midway, the cleanup path calls bpf_cgroup_storages_free(new_storage) to free the newly allocated storage, but fails to restore pl->storage back to old_storage. Consequently, the still-active prog1 holds invalid or dangling storage pointers, leading to an invalid memory access when prog1 executes and calls bpf_get_local_storage. Additionally, original pl->flags and cgrp->bpf.flags[atype] are left unrestored. Fix this by saving old_pl_flags, old_storage, and old_flags prior to the update, and properly restoring all of them in the cleanup path on error.

References

NVD — CVE-2026-90313 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90313
git.kernel.org/stable/c/2c2218560b... WEB
https://git.kernel.org/stable/c/2c2218560b6e28a63ff7834ba26d09ff8efdee39
git.kernel.org/stable/c/6655c40970... WEB
https://git.kernel.org/stable/c/6655c409707ec8ce9ce0850ffe4fe02331fd4d9c
git.kernel.org/stable/c/86ead17630... WEB
https://git.kernel.org/stable/c/86ead176301109b78e1d14c0e9d0d9ff9723c769
git.kernel.org/stable/c/aaca16e042... WEB
https://git.kernel.org/stable/c/aaca16e042527f7efe48b50799bc662f1a191ce1
git.kernel.org/stable/c/e26db0d636... WEB
https://git.kernel.org/stable/c/e26db0d636e4c24a6b16683ea95cf5077c64d74b

Frequently Asked Questions

What is CVE-2026-90313?
CVE-2026-90313 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-90313?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90313?
CVE-2026-90313 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90313?
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-2mrf-g72x-r6vx",
  "modified" : "2026-09-17T18:32:00Z",
  "published" : "2026-09-17T18:32:00Z",
  "aliases" : [ "CVE-2026-90313" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed\n\nA potential invalid storage access issue can occur after replacing a\ncgroup bpf prog.\n\nThis occurs in the following scenario:\n1. prog1 with storage is attached to a cgroup in multi-attach mode.\n2. prog1 is replaced with prog2 using BPF_F_REPLACE in multi-attach\n   mode, but fails midway (e.g. in bpf_trampoline_link_cgroup_shim or\n   update_effective_progs).\n3. A new prog3 is attached to the cgroup in multi-attach mode.\n\nThe reason is that __cgroup_bpf_attach overwrites pl->storage with the\nnew storage prior to attachment completion. When attachment fails\nmidway, the cleanup path calls bpf_cgroup_storages_free(new_storage) to\nfree the newly allocated storage, but fails to restore pl->storage back\nto old_storage.\n\nConsequently, the still-active prog1 holds invalid or dangling storage\npointers, leading to an invalid memory access when prog1 executes and\ncalls bpf_get_local_storage. Additionally, original pl->flags and\ncgrp->bpf.flags[atype] are left unrestored.\n\nFix this by saving old_pl_flags, old_storage, and old_flags prior to the\nupdate, and properly restoring all of them in the cleanup path on error.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90313"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2c2218560b6e28a63ff7834ba26d09ff8efdee39"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6655c409707ec8ce9ce0850ffe4fe02331fd4d9c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/86ead176301109b78e1d14c0e9d0d9ff9723c769"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aaca16e042527f7efe48b50799bc662f1a191ce1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e26db0d636e4c24a6b16683ea95cf5077c64d74b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:29Z"
  }
}