CVE-2026-90261: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-6683-vc4x-94r5
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90261
GHSA Identifier GHSA-6683-vc4x-94r5
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-90261

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-90261, 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: btrfs: zoned: flush active metadata block group at btree_writepages() start btree_writepages() writes the btree inode's dirty metadata in ascending logical address order. On a zoned filesystem only one metadata and one system block group is active for writing at a time, and check_bg_is_active() (via btrfs_check_meta_write_pointer()) pivots the active block group as writeback moves from one block group to the next. If the active block group sits at a higher logical address than another block group that also holds dirty metadata, the ascending walk reaches the lower one first and, to write it, has to finish the active block group and activate the lower one. It cannot finish a block group that still has unsent IO, and during WB_SYNC_ALL && !for_sync (commit) writeback it deliberately refuses to wait for that IO under fs_info->zoned_meta_io_lock, as that can deadlock. The pivot thus cannot issue the submission itself either, so it gives up: btrfs_check_meta_write_pointer() returns -EAGAIN, which btrfs_write_and_wait_transaction() treats as fatal and aborts the transaction, forcing the filesystem read-only. This happens intermittently under metadata-heavy relocation (e.g. fstests btrfs/187). Flush the active metadata and system block groups at the start of btree_writepages(), under the fs_info->zoned_meta_io_lock it already holds, so they have no unsent IO left and the later pivot can finish them and make forward progress.

References

NVD — CVE-2026-90261 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90261
git.kernel.org/stable/c/58b0ab0340... WEB
https://git.kernel.org/stable/c/58b0ab0340ce04a057169d42cbacbf786063813d
git.kernel.org/stable/c/e2de2989ad... WEB
https://git.kernel.org/stable/c/e2de2989adb3e58c2320e57c255f52e065667b5e
git.kernel.org/stable/c/ecc05eda9a... WEB
https://git.kernel.org/stable/c/ecc05eda9a346848ae01a6c8bfa3f0bec133bd8b

Frequently Asked Questions

What is CVE-2026-90261?
CVE-2026-90261 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-90261?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90261?
CVE-2026-90261 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90261?
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-6683-vc4x-94r5",
  "modified" : "2026-10-15T12:30:49Z",
  "published" : "2026-09-17T18:31:58Z",
  "aliases" : [ "CVE-2026-90261" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: flush active metadata block group at btree_writepages() start\n\nbtree_writepages() writes the btree inode's dirty metadata in ascending\nlogical address order. On a zoned filesystem only one metadata and one\nsystem block group is active for writing at a time, and\ncheck_bg_is_active() (via btrfs_check_meta_write_pointer()) pivots the\nactive block group as writeback moves from one block group to the next.\n\nIf the active block group sits at a higher logical address than another\nblock group that also holds dirty metadata, the ascending walk reaches\nthe lower one first and, to write it, has to finish the active block\ngroup and activate the lower one. It cannot finish a block group that\nstill has unsent IO, and during WB_SYNC_ALL && !for_sync (commit)\nwriteback it deliberately refuses to wait for that IO under\nfs_info->zoned_meta_io_lock, as that can deadlock. The pivot thus cannot\nissue the submission itself either, so it gives up:\nbtrfs_check_meta_write_pointer() returns -EAGAIN, which\nbtrfs_write_and_wait_transaction() treats as fatal and aborts the\ntransaction, forcing the filesystem read-only. This happens\nintermittently under metadata-heavy relocation (e.g. fstests btrfs/187).\n\nFlush the active metadata and system block groups at the start of\nbtree_writepages(), under the fs_info->zoned_meta_io_lock it already\nholds, so they have no unsent IO left and the later pivot can finish\nthem and make forward progress.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90261"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/58b0ab0340ce04a057169d42cbacbf786063813d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e2de2989adb3e58c2320e57c255f52e065667b5e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ecc05eda9a346848ae01a6c8bfa3f0bec133bd8b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:22Z"
  }
}