CVE-2026-93140: Software Security Vulnerability Vulnerability

UNKNOWN

Advisory Identifier: GHSA-hwwj-mw3q-359r

Published 2026-09-17

Advisory Summary

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

CVE Identifier CVE-2026-93140

GHSA Identifier GHSA-hwwj-mw3q-359r

Severity N/A

CVSS v3.1 Base Score N/A

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-09-17

Last Updated 2026-09-17

How to Fix CVE-2026-93140

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-93140, 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: udf: Mark LVID buffer as uptodate before marking it dirty When an I/O error occurs while writing the Logical Volume Integrity Descriptor (LVID) buffer to the block device, the block layer's completion handler (`end_buffer_write_sync()`) clears the `BH_Uptodate` flag on the buffer. However, the buffer still contains valid LVID data in memory. If the filesystem is subsequently remounted read-write or synced, `udf_open_lvid()` or `udf_sync_fs()` will modify the LVID buffer and call `mark_buffer_dirty()`. This triggers a spurious `WARN_ON_ONCE(!buffer_uptodate(bh))` warning in `mark_buffer_dirty()` because the buffer is not marked uptodate, even though its in-memory contents are valid and are about to be overwritten. To prevent this spurious warning, unconditionally set the `BH_Uptodate` flag before calling `mark_buffer_dirty()` in `udf_open_lvid()` and `udf_sync_fs()`. This acknowledges that the in-memory buffer is valid and matches the workaround previously applied to `udf_close_lvid()` in commit 853a0c25baf9 ("udf: Mark LVID buffer as uptodate before marking it dirty"). Extending this workaround ensures consistent behavior across all LVID updates. Buffer I/O error on dev loop0, logical block 128, lost sync page write ------------[ cut here ]------------ !buffer_uptodate(bh) WARNING: fs/buffer.c:1087 at mark_buffer_dirty+0x299/0x410 fs/buffer.c:1087 ... Call Trace: <TASK> udf_open_lvid+0x369/0x5b0 fs/udf/super.c:2078 udf_reconfigure+0x336/0x540 fs/udf/super.c:679 reconfigure_super+0x232/0x8f0 fs/super.c:1080 vfs_cmd_reconfigure fs/fsopen.c:268 [inline] vfs_fsconfig_locked+0x171/0x320 fs/fsopen.c:297 __do_sys_fsconfig fs/fsopen.c:463 [inline] __se_sys_fsconfig+0x6b9/0x810 fs/fsopen.c:350 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94 </TASK>

References

NVD — CVE-2026-93140 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-93140

git.kernel.org/stable/c/11afe19121... WEB

https://git.kernel.org/stable/c/11afe1912140f79d5af3091a54b181ef72fce1a5

git.kernel.org/stable/c/359cea636f... WEB

https://git.kernel.org/stable/c/359cea636f4a74a96c01a8050f155e12840c079a

git.kernel.org/stable/c/8034ddf475... WEB

https://git.kernel.org/stable/c/8034ddf4751d9143c5ef7eebe3d4f33218fdd378

git.kernel.org/stable/c/a4c4e38b35... WEB

https://git.kernel.org/stable/c/a4c4e38b356ad4c1f90478124922917489137c08

git.kernel.org/stable/c/c4058355d2... WEB

https://git.kernel.org/stable/c/c4058355d27488a3cd31c60c032335f77c4fdcfc

git.kernel.org/stable/c/e6461ef34f... WEB

https://git.kernel.org/stable/c/e6461ef34f91ad7dbffdf912b3d661a7dd892931

git.kernel.org/stable/c/ee477e5204... WEB

https://git.kernel.org/stable/c/ee477e5204f764444e60699280abf5936c2a6ae6

git.kernel.org/stable/c/fb0601134c... WEB

https://git.kernel.org/stable/c/fb0601134c7e51728bd098abc6909315de1e5d86

Frequently Asked Questions

What is CVE-2026-93140?

CVE-2026-93140 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-93140?

Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.

What CWE is associated with CVE-2026-93140?

CVE-2026-93140 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2026-93140?

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-hwwj-mw3q-359r",
  "modified" : "2026-09-17T18:32:12Z",
  "published" : "2026-09-17T18:32:11Z",
  "aliases" : [ "CVE-2026-93140" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nudf: Mark LVID buffer as uptodate before marking it dirty\n\nWhen an I/O error occurs while writing the Logical Volume Integrity\nDescriptor (LVID) buffer to the block device, the block layer's completion\nhandler (`end_buffer_write_sync()`) clears the `BH_Uptodate` flag on the\nbuffer. However, the buffer still contains valid LVID data in memory. If\nthe filesystem is subsequently remounted read-write or synced,\n`udf_open_lvid()` or `udf_sync_fs()` will modify the LVID buffer and call\n`mark_buffer_dirty()`. This triggers a spurious\n`WARN_ON_ONCE(!buffer_uptodate(bh))` warning in `mark_buffer_dirty()`\nbecause the buffer is not marked uptodate, even though its in-memory\ncontents are valid and are about to be overwritten.\n\nTo prevent this spurious warning, unconditionally set the `BH_Uptodate`\nflag before calling `mark_buffer_dirty()` in `udf_open_lvid()` and\n`udf_sync_fs()`. This acknowledges that the in-memory buffer is valid and\nmatches the workaround previously applied to `udf_close_lvid()` in commit\n853a0c25baf9 (\"udf: Mark LVID buffer as uptodate before marking it dirty\").\nExtending this workaround ensures consistent behavior across all LVID\nupdates.\n\nBuffer I/O error on dev loop0, logical block 128, lost sync page write\n------------[ cut here ]------------\n!buffer_uptodate(bh)\nWARNING: fs/buffer.c:1087 at mark_buffer_dirty+0x299/0x410 fs/buffer.c:1087\n...\nCall Trace:\n <TASK>\n udf_open_lvid+0x369/0x5b0 fs/udf/super.c:2078\n udf_reconfigure+0x336/0x540 fs/udf/super.c:679\n reconfigure_super+0x232/0x8f0 fs/super.c:1080\n vfs_cmd_reconfigure fs/fsopen.c:268 [inline]\n vfs_fsconfig_locked+0x171/0x320 fs/fsopen.c:297\n __do_sys_fsconfig fs/fsopen.c:463 [inline]\n __se_sys_fsconfig+0x6b9/0x810 fs/fsopen.c:350\n do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94\n </TASK>",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93140"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/11afe1912140f79d5af3091a54b181ef72fce1a5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/359cea636f4a74a96c01a8050f155e12840c079a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8034ddf4751d9143c5ef7eebe3d4f33218fdd378"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a4c4e38b356ad4c1f90478124922917489137c08"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c4058355d27488a3cd31c60c032335f77c4fdcfc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e6461ef34f91ad7dbffdf912b3d661a7dd892931"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ee477e5204f764444e60699280abf5936c2a6ae6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fb0601134c7e51728bd098abc6909315de1e5d86"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:18:08Z"
  }
}

Advisory Metadata

Source ID: GHSA-hwwj-mw3q-359r
Schema Version: 1.4.0
Published: 2026-09-17 18:32
Last Modified: 2026-09-17 18:32
Database Record File: advisories/unreviewed/2026/09/GHSA-hwwj-mw3q-359r/GHSA-hwwj-mw3q-359r.json