CVE-2026-90185: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-66h5-crgq-784h
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90185
GHSA Identifier GHSA-66h5-crgq-784h
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-90185

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-90185, 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: null_blk: serialize configfs attribute stores with the lock The NULLB_DEVICE_ATTR _store takes no lock: apply_fn attributes (submit_queues, poll_queues) get dev->NAME written again after apply_fn returns, outside its lock; APPLY=NULL attributes are entirely lockless. configfs only serializes stores per-open-file, so concurrent stores on separate fds race. For apply_fn attributes, once one store's apply_fn has reconfigured the hardware, a second (losing) store can still overwrite dev->NAME afterwards. This leaves dev->submit_queues out of sync with the live queue count, which is later caught by the WARN_ON_ONCE() in null_map_queues(). For !apply_fn attributes, power_store()'s null_add_dev() validates and builds the device under "lock" but only sets CONFIGURED afterwards. A store slipping in during this window can change a field mid-setup -- for example, zone_nr_conv can be pushed above nr_zones after it has already been clamped, leading to an out-of-bounds dev->zones[] access. Take "lock" in the macro around the apply_fn call, the CONFIGURED test and the field write, and move it out of nullb_apply_submit_queues()/ nullb_apply_poll_queues() so both paths are covered once. This serializes stores with power_store's setup and with each other.

References

NVD — CVE-2026-90185 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90185
git.kernel.org/stable/c/3945ce8cbc... WEB
https://git.kernel.org/stable/c/3945ce8cbce4e328e6fdf0b522dc71e340de19db
git.kernel.org/stable/c/65cae82fd3... WEB
https://git.kernel.org/stable/c/65cae82fd3c39b53430672cb9e3ecd267471a6ce
git.kernel.org/stable/c/7e7fff5180... WEB
https://git.kernel.org/stable/c/7e7fff51808237703a3a1df6dd5cae1dfd1db86d
git.kernel.org/stable/c/88d806d0e1... WEB
https://git.kernel.org/stable/c/88d806d0e1d36246208386a8e55b511c1b3d647c
git.kernel.org/stable/c/8e839ed521... WEB
https://git.kernel.org/stable/c/8e839ed5210399a0330a8a6c5885c1d40a537c6d
git.kernel.org/stable/c/c70994c286... WEB
https://git.kernel.org/stable/c/c70994c2862b05e44728912b2ea9487d31e2aea7

Frequently Asked Questions

What is CVE-2026-90185?
CVE-2026-90185 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-90185?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90185?
CVE-2026-90185 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90185?
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-66h5-crgq-784h",
  "modified" : "2026-09-17T18:31:54Z",
  "published" : "2026-09-17T18:31:54Z",
  "aliases" : [ "CVE-2026-90185" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: serialize configfs attribute stores with the lock\n\nThe NULLB_DEVICE_ATTR _store takes no lock: apply_fn attributes\n(submit_queues, poll_queues) get dev->NAME written again after apply_fn\nreturns, outside its lock; APPLY=NULL attributes are entirely lockless.\nconfigfs only serializes stores per-open-file, so concurrent stores on\nseparate fds race.\n\nFor apply_fn attributes, once one store's apply_fn has reconfigured the\nhardware, a second (losing) store can still overwrite dev->NAME\nafterwards. This leaves dev->submit_queues out of sync with the live\nqueue count, which is later caught by the WARN_ON_ONCE() in\nnull_map_queues().\n\nFor !apply_fn attributes, power_store()'s null_add_dev() validates and\nbuilds the device under \"lock\" but only sets CONFIGURED afterwards. A store\nslipping in during this window can change a field mid-setup -- for example,\nzone_nr_conv can be pushed above nr_zones after it has already been\nclamped, leading to an out-of-bounds dev->zones[] access.\n\nTake \"lock\" in the macro around the apply_fn call, the CONFIGURED test and\nthe field write, and move it out of nullb_apply_submit_queues()/\nnullb_apply_poll_queues() so both paths are covered once. This serializes\nstores with power_store's setup and with each other.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90185"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3945ce8cbce4e328e6fdf0b522dc71e340de19db"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/65cae82fd3c39b53430672cb9e3ecd267471a6ce"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7e7fff51808237703a3a1df6dd5cae1dfd1db86d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/88d806d0e1d36246208386a8e55b511c1b3d647c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8e839ed5210399a0330a8a6c5885c1d40a537c6d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c70994c2862b05e44728912b2ea9487d31e2aea7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:12Z"
  }
}