CVE-2026-93255: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-vp7r-5mv7-7v8c
Published
Advisory Summary

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

CVE Identifier CVE-2026-93255
GHSA Identifier GHSA-vp7r-5mv7-7v8c
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-93255

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-93255, 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: make sure EXTENT_BUFFER_READING is cleared under refs_lock [FALSE ALERTS] There is a bug report that the warning inside invalidate_and_check_btree_folios() got triggered during btrfs/298: BTRFS info (device sdd): first mount of filesystem f9bf732a-a19b-44b9-99a7-614ddff168e2 BTRFS info (device sdd): using crc32c checksum algorithm BTRFS error (device sdd): failed to find fsid cb2fdb42-b638-4f2f-badd-4127467ba674 when attempting to open seed devices BTRFS error (device sdd): failed to read chunk tree: -2 ------------[ cut here ]------------ WARNING: disk-io.c:3342 at invalidate_and_check_btree_folios+0x260/0x3c0 [btrfs], CPU#4: mount/125993 CPU: 4 UID: 0 PID: 125993 Comm: mount Tainted: G W OE 7.1.0-rc7-custom+ #1 PREEMPT(full) Hardware name: QEMU KVM Virtual Machine, BIOS edk2-20250812-19.fc42 08/12/2025 Call trace: invalidate_and_check_btree_folios+0x260/0x3c0 [btrfs] (P) open_ctree+0x1f50/0x23b0 [btrfs] btrfs_get_tree+0x89c/0xc48 [btrfs] vfs_get_tree+0x30/0x110 vfs_cmd_create+0x58/0xe8 __arm64_sys_fsconfig+0x39c/0x518 invoke_syscall.constprop.0+0x48/0x120 el0_svc_common.constprop.0+0x40/0xe8 do_el0_svc+0x24/0x38 el0_svc+0x50/0x310 el0t_64_sync_handler+0xa0/0xe8 el0t_64_sync+0x198/0x1a0 ---[ end trace 0000000000000000 ]--- BTRFS warning (device sdd): unable to release extent buffer 365985792 owner 3 gen 17 refs 3 flags 0x5 [CAUSE] In that invalidate_and_check_btree_folios() we wait for the eb to finish its read, then check if it's only held by us and the btree inode. If not, then do a warning as it may be still held, and could cause problems. But there is a small window where the check can lead to false alerts: Thread A (Read endio) | Thread B (Unmount) ----------------------------------+------------------------------------- end_bbio_meta_read() | | The eb has one extra ref held | | by the reader, and has | | EXTENT_BUFFER_READING flag set | invalidate_and_check_btree_folios() | | | |- clear_extent_buffer_reading() | | | | |- wait_on_bit_io(); | | | The EXTENT_BUFFER_READING flag is | | | cleared | | |- if (refcount_read(eb->refs) > 2) | | The eb is held by the read, us | | and btree inode, thus it | | will trigger the warning |- free_extent_buffer() | [FIX] Introduce a helper, free_extent_buffer_clear_reading(). If the new parameter, @clear_reading, is set, we will hold the spinlock at the beginning of free_extent_buffer_clear_reading() to make sure the EXTENT_BUFFER_READING flag is cleared inside the same critical section of decreasing refs. Now free_extent_buffer() will just call free_extent_buffer_clear_reading() with @clear_reading set to false, so no behavior change. But for end_bbio_meta_read(), it will not clear_extent_buffer_reading() directly, but pass @clear_reading as true. Then inside invalidate_and_check_btree_folios(), hold the refs_lock before reading refs. So that we eliminate the race window completely.

References

Frequently Asked Questions

What is CVE-2026-93255?
CVE-2026-93255 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-93255?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93255?
CVE-2026-93255 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93255?
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-vp7r-5mv7-7v8c",
  "modified" : "2026-10-15T12:30:53Z",
  "published" : "2026-09-24T18:31:24Z",
  "aliases" : [ "CVE-2026-93255" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: make sure EXTENT_BUFFER_READING is cleared under refs_lock\n\n[FALSE ALERTS]\nThere is a bug report that the warning inside\ninvalidate_and_check_btree_folios() got triggered during btrfs/298:\n\n BTRFS info (device sdd): first mount of filesystem f9bf732a-a19b-44b9-99a7-614ddff168e2\n BTRFS info (device sdd): using crc32c checksum algorithm\n BTRFS error (device sdd): failed to find fsid cb2fdb42-b638-4f2f-badd-4127467ba674 when attempting to open seed devices\n BTRFS error (device sdd): failed to read chunk tree: -2\n ------------[ cut here ]------------\n WARNING: disk-io.c:3342 at invalidate_and_check_btree_folios+0x260/0x3c0 [btrfs], CPU#4: mount/125993\n CPU: 4 UID: 0 PID: 125993 Comm: mount Tainted: G        W  OE       7.1.0-rc7-custom+ #1 PREEMPT(full)\n Hardware name: QEMU KVM Virtual Machine, BIOS edk2-20250812-19.fc42 08/12/2025\n Call trace:\n  invalidate_and_check_btree_folios+0x260/0x3c0 [btrfs] (P)\n  open_ctree+0x1f50/0x23b0 [btrfs]\n  btrfs_get_tree+0x89c/0xc48 [btrfs]\n  vfs_get_tree+0x30/0x110\n  vfs_cmd_create+0x58/0xe8\n  __arm64_sys_fsconfig+0x39c/0x518\n  invoke_syscall.constprop.0+0x48/0x120\n  el0_svc_common.constprop.0+0x40/0xe8\n  do_el0_svc+0x24/0x38\n  el0_svc+0x50/0x310\n  el0t_64_sync_handler+0xa0/0xe8\n  el0t_64_sync+0x198/0x1a0\n ---[ end trace 0000000000000000 ]---\n BTRFS warning (device sdd): unable to release extent buffer 365985792 owner 3 gen 17 refs 3 flags 0x5\n\n[CAUSE]\nIn that invalidate_and_check_btree_folios() we wait for the eb to finish\nits read, then check if it's only held by us and the btree inode.\n\nIf not, then do a warning as it may be still held, and could cause\nproblems.\n\nBut there is a small window where the check can lead to false alerts:\n\n    Thread A (Read endio)         |        Thread B (Unmount)\n----------------------------------+-------------------------------------\n end_bbio_meta_read()             |\n | The eb has one extra ref held  |\n | by the reader, and has         |\n | EXTENT_BUFFER_READING flag set | invalidate_and_check_btree_folios()\n |                                | |\n |- clear_extent_buffer_reading() | |\n |                                | |- wait_on_bit_io();\n |                                | |  The EXTENT_BUFFER_READING flag is\n |                                | |  cleared\n |                                | |- if (refcount_read(eb->refs) > 2)\n |                                |    The eb is held by the read, us\n |                                |    and btree inode, thus it\n |                                |    will trigger the warning\n |- free_extent_buffer()          |\n\n[FIX]\nIntroduce a helper, free_extent_buffer_clear_reading().\n\nIf the new parameter, @clear_reading, is set, we will hold the spinlock\nat the beginning of free_extent_buffer_clear_reading() to make sure the\nEXTENT_BUFFER_READING flag is cleared inside the same critical section\nof decreasing refs.\n\nNow free_extent_buffer() will just call\nfree_extent_buffer_clear_reading() with @clear_reading set to false, so\nno behavior change.\n\nBut for end_bbio_meta_read(), it will not clear_extent_buffer_reading()\ndirectly, but pass @clear_reading as true.\n\nThen inside invalidate_and_check_btree_folios(), hold the refs_lock\nbefore reading refs.\nSo that we eliminate the race window completely.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93255"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2073f3d97b0c5d34fe64812d1237e37bd79c17ec"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/690c2accacb1aca91ab8186d15dee56da8723f31"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8f7285d608ed0db7c9f09f341547db5ce1351090"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-24T16:17:22Z"
  }
}