CVE-2026-90276: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-wg47-q44p-vcm3
Published
Advisory Summary

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

CVE Identifier CVE-2026-90276
GHSA Identifier GHSA-wg47-q44p-vcm3
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-90276

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-90276, 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/md-llbitmap: stop daemon timer rearm on destroy llbitmap_destroy() deletes pending_timer before flushing md_llbitmap_io_wq. However, daemon_work can still be queued or running after the timer has been deleted, and the daemon path can arm pending_timer again when it finds dirty chunks that are not ready to flush yet. If that happens during teardown, pending_timer can remain armed after llbitmap is freed and later dereference freed memory. Add a BITMAP_SHUTDOWN bit to llbitmap->flags, set it before deleting the timer, and make the timer and daemon paths stop queueing or rearming work once teardown starts. Cancel daemon_work before flushing the shared workqueue so no already queued daemon instance can race with the free. Use timer_shutdown_sync() so a daemon instance that passed the shutdown check before teardown cannot rearm the timer afterward. BITMAP_SHUTDOWN is a runtime-only state. Mask it out when reading and updating the llbitmap superblock so the shutdown state is never loaded from disk or persisted to disk.

References

Frequently Asked Questions

What is CVE-2026-90276?
CVE-2026-90276 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-90276?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90276?
CVE-2026-90276 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90276?
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-wg47-q44p-vcm3",
  "modified" : "2026-09-17T18:31:58Z",
  "published" : "2026-09-17T18:31:58Z",
  "aliases" : [ "CVE-2026-90276" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/md-llbitmap: stop daemon timer rearm on destroy\n\nllbitmap_destroy() deletes pending_timer before flushing\nmd_llbitmap_io_wq. However, daemon_work can still be queued or running\nafter the timer has been deleted, and the daemon path can arm\npending_timer again when it finds dirty chunks that are not ready to\nflush yet.\n\nIf that happens during teardown, pending_timer can remain armed after\nllbitmap is freed and later dereference freed memory.\n\nAdd a BITMAP_SHUTDOWN bit to llbitmap->flags, set it before deleting\nthe timer, and make the timer and daemon paths stop queueing or rearming\nwork once teardown starts. Cancel daemon_work before flushing the shared\nworkqueue so no already queued daemon instance can race with the free.\nUse timer_shutdown_sync() so a daemon instance that passed the shutdown\ncheck before teardown cannot rearm the timer afterward.\n\nBITMAP_SHUTDOWN is a runtime-only state. Mask it out when reading and\nupdating the llbitmap superblock so the shutdown state is never loaded\nfrom disk or persisted to disk.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90276"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5553d64e01d9a995be6c3de38501c6dd4ceede3b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bb7f92d58fca9a9f06f3f51a82481c5f0bbbd46c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c55aa6c17f019b6296952d336939891efa084c06"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:24Z"
  }
}