CVE-2026-64326: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-h8v6-c5rc-5j48
Share
CVSS 5.5
Published
Advisory Summary

CVE-2026-64326 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-64326 at a Glance

CVE Identifier CVE-2026-64326
GHSA Identifier GHSA-h8v6-c5rc-5j48
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-64326

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-64326, 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: block: skip sync_blockdev() on surprise removal in bdev_mark_dead() bdev_mark_dead()'s @surprise == true means the device is already gone. The filesystem callback fs_bdev_mark_dead() honours this and skips sync_filesystem(), but the bare block device path (no ->mark_dead op) lost its !surprise guard when the holder ->mark_dead callback was wired up (see Fixes), and now calls sync_blockdev() unconditionally, which can hang forever waiting on writeback that can no longer complete. syzkaller hit this via nvme_reset_work()'s "I/O queues lost" path: nvme_mark_namespaces_dead() -> blk_mark_disk_dead() -> bdev_mark_dead(bdev, true) -> sync_blockdev() blocks in folio_wait_writeback(), wedging the reset worker and every task waiting on it. Skip the sync on surprise removal, matching fs_bdev_mark_dead(); invalidate_bdev() still runs. Orderly removal (surprise == false) is unchanged. Found by FuzzNvme(Syzkaller with FEMU fuzzing framework).

References

NVD — CVE-2026-64326 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64326
git.kernel.org/stable/c/49f06cff50... WEB
https://git.kernel.org/stable/c/49f06cff50a4ccf3b7a1a662ceb892b3b21a527a
git.kernel.org/stable/c/9818bcae3c... WEB
https://git.kernel.org/stable/c/9818bcae3c0ca1dde4b9a334125c46676e0a9b29
git.kernel.org/stable/c/aa4c4a9315... WEB
https://git.kernel.org/stable/c/aa4c4a9315764b2b7a7182e72cc5ea87520436b4
git.kernel.org/stable/c/d6998ddd50... WEB
https://git.kernel.org/stable/c/d6998ddd507c81e3829489a6ead23f17f5acb7fe
git.kernel.org/stable/c/f41cf35ee2... WEB
https://git.kernel.org/stable/c/f41cf35ee2a1e31374b3f54e7579c55153506e70

Frequently Asked Questions

What is CVE-2026-64326?
CVE-2026-64326 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-64326?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-64326?
CVE-2026-64326 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-64326?
CVE-2026-64326 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-64326?
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-h8v6-c5rc-5j48",
  "modified" : "2026-09-04T15:35:50Z",
  "published" : "2026-07-25T12:31:31Z",
  "aliases" : [ "CVE-2026-64326" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: skip sync_blockdev() on surprise removal in bdev_mark_dead()\n\nbdev_mark_dead()'s @surprise == true means the device is already gone.\nThe filesystem callback fs_bdev_mark_dead() honours this and skips\nsync_filesystem(), but the bare block device path (no ->mark_dead op)\nlost its !surprise guard when the holder ->mark_dead callback was wired\nup (see Fixes), and now calls sync_blockdev() unconditionally, which can\nhang forever waiting on writeback that can no longer complete.\n\nsyzkaller hit this via nvme_reset_work()'s \"I/O queues lost\" path:\nnvme_mark_namespaces_dead() -> blk_mark_disk_dead() ->\nbdev_mark_dead(bdev, true) -> sync_blockdev() blocks in\nfolio_wait_writeback(), wedging the reset worker and every task waiting\non it.\n\nSkip the sync on surprise removal, matching fs_bdev_mark_dead();\ninvalidate_bdev() still runs. Orderly removal (surprise == false) is\nunchanged.\n\nFound by FuzzNvme(Syzkaller with FEMU fuzzing framework).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64326"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/49f06cff50a4ccf3b7a1a662ceb892b3b21a527a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9818bcae3c0ca1dde4b9a334125c46676e0a9b29"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aa4c4a9315764b2b7a7182e72cc5ea87520436b4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d6998ddd507c81e3829489a6ead23f17f5acb7fe"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f41cf35ee2a1e31374b3f54e7579c55153506e70"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-25T10:17:14Z"
  }
}