CVE-2026-90005: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-rjc9-q3q5-8f95
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90005
GHSA Identifier GHSA-rjc9-q3q5-8f95
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-90005

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-90005, 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: samples/damon/wsse: handle damon_start() failure Patch series "samples/damon: handle damon_{start,stop}() failures". All DAMON sample modules are not correctly handling failures from damon_start(). Among those, mtier also has an additional problem for handling of damon_stop() failures. wsse and prcl also have a problem in their damon_call() failure handling. As a result, memory leaks, next DAMON operation disruptions, and use-after-free can happen. Fix those. Note that only the damon_start() failure caused issues can reliably be reproduced. Reproducing those issues require the admin permission, though. This patch (of 6): damon_sample_wsse_start() callers assume it will clean up resources when it fails. And the function does the cleanup for context buildup failures. However, it is not doing the cleanup for damon_start() failure. As a result, when damon_start() fails, it leaks the memory for DAMON context. Free the context in case of the failure to fix the issues. Note that the issue can reliably be reproduced because the module calls damon_start() in the exclusive mode. For example, $ sudo damo start $ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid $ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled $ sudo cat /proc/allocinfo | grep damon_new_ctx Because the first command is running another DAMON instance, the third command fails the damon_start() call because the new DAMON instance cannot exclusively run. And without this fix, by repeating the third and the fourth commands above, we can show the memory consumption is only increasing due to the leaks. It requires the sudo permission though. The issue was discovered [1] by Sashiko.

References

NVD — CVE-2026-90005 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90005
git.kernel.org/stable/c/6179c7f478... WEB
https://git.kernel.org/stable/c/6179c7f47876d576dfe30efa8fbf1b0b1fdd13c0
git.kernel.org/stable/c/e4742be45e... WEB
https://git.kernel.org/stable/c/e4742be45ea45bf554399ce89a09f71e525d7981
git.kernel.org/stable/c/e60774d633... WEB
https://git.kernel.org/stable/c/e60774d6335b89fac0be8b17a041fcffc508d281

Frequently Asked Questions

What is CVE-2026-90005?
CVE-2026-90005 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-90005?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90005?
CVE-2026-90005 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90005?
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-rjc9-q3q5-8f95",
  "modified" : "2026-09-16T12:30:45Z",
  "published" : "2026-09-16T12:30:45Z",
  "aliases" : [ "CVE-2026-90005" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsamples/damon/wsse: handle damon_start() failure\n\nPatch series \"samples/damon: handle damon_{start,stop}() failures\".\n\nAll DAMON sample modules are not correctly handling failures from\ndamon_start().  Among those, mtier also has an additional problem for\nhandling of damon_stop() failures.  wsse and prcl also have a problem in\ntheir damon_call() failure handling.  As a result, memory leaks, next\nDAMON operation disruptions, and use-after-free can happen.  Fix those.\n\nNote that only the damon_start() failure caused issues can reliably be\nreproduced.  Reproducing those issues require the admin permission,\nthough.\n\n\nThis patch (of 6):\n\ndamon_sample_wsse_start() callers assume it will clean up resources when\nit fails.  And the function does the cleanup for context buildup failures.\nHowever, it is not doing the cleanup for damon_start() failure.  As a\nresult, when damon_start() fails, it leaks the memory for DAMON context. \nFree the context in case of the failure to fix the issues.\n\nNote that the issue can reliably be reproduced because the module calls\ndamon_start() in the exclusive mode.  For example,\n\n    $ sudo damo start\n    $ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid\n    $ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled\n    $ sudo cat /proc/allocinfo | grep damon_new_ctx\n\nBecause the first command is running another DAMON instance, the third\ncommand fails the damon_start() call because the new DAMON instance cannot\nexclusively run.  And without this fix, by repeating the third and the\nfourth commands above, we can show the memory consumption is only\nincreasing due to the leaks.  It requires the sudo permission though.\n\nThe issue was discovered [1] by Sashiko.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90005"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6179c7f47876d576dfe30efa8fbf1b0b1fdd13c0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e4742be45ea45bf554399ce89a09f71e525d7981"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e60774d6335b89fac0be8b17a041fcffc508d281"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:13Z"
  }
}