CVE-2026-90275: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-c82r-j325-qwcg
Published
Advisory Summary

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

CVE Identifier CVE-2026-90275
GHSA Identifier GHSA-c82r-j325-qwcg
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-90275

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-90275, 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: md/raid1: don't set array_frozen in raid1_takeover() raid1_takeover() sets conf->array_frozen = 1 on the newly-allocated r1conf and nothing ever clears it, so every I/O to the array stalls permanently once _wait_barrier() sees it stuck at 1. This used to be harmless: level_store() called mddev_resume() right after pers->run(), which called raid1_quiesce(mddev, 0) and cleared array_frozen back to 0 regardless of what raid1_takeover() set. Commit b39f35ebe86d ("md: don't quiesce in mddev_suspend()") removed that quiesce(mddev, 0) call, so the pre-set now sticks. setup_conf() already zero-initializes the new r1conf via kzalloc, so just don't set array_frozen here. Same class of bug as commit 892da88d1cd9 ("md/raid10: fix a 'conf->barrier' leakage in raid10_takeover()"), also triggered by b39f35ebe86d.

References

Frequently Asked Questions

What is CVE-2026-90275?
CVE-2026-90275 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-90275?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90275?
CVE-2026-90275 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90275?
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-c82r-j325-qwcg",
  "modified" : "2026-09-17T18:31:58Z",
  "published" : "2026-09-17T18:31:58Z",
  "aliases" : [ "CVE-2026-90275" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid1: don't set array_frozen in raid1_takeover()\n\nraid1_takeover() sets conf->array_frozen = 1 on the newly-allocated\nr1conf and nothing ever clears it, so every I/O to the array stalls\npermanently once _wait_barrier() sees it stuck at 1.\n\nThis used to be harmless: level_store() called mddev_resume() right\nafter pers->run(), which called raid1_quiesce(mddev, 0) and cleared\narray_frozen back to 0 regardless of what raid1_takeover() set. Commit\nb39f35ebe86d (\"md: don't quiesce in mddev_suspend()\") removed that\nquiesce(mddev, 0) call, so the pre-set now sticks.\n\nsetup_conf() already zero-initializes the new r1conf via kzalloc, so\njust don't set array_frozen here.\n\nSame class of bug as commit 892da88d1cd9 (\"md/raid10: fix a\n'conf->barrier' leakage in raid10_takeover()\"), also triggered by\nb39f35ebe86d.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90275"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/668d99ba47210ab6ceb18f1cf022c0accca7e3bb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b6ec4bf1ec4446c0213c08ea493e48e6b83cd1af"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c57ec2749ee03cace564eec7bb37c89dc3d8d47b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dc386aa0ac0a3ec06c9a3ea9b064b073fb72a916"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f9cdb5bb8efbf401e84d850828271af87e6be2dc"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:24Z"
  }
}