CVE-2026-64359: Software Security Vulnerability Vulnerability

MODERATE

Advisory Identifier: GHSA-7cjq-w44j-qx9w

CVSS 5.5

Published 2026-07-25

Advisory Summary

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

CVE Identifier CVE-2026-64359

GHSA Identifier GHSA-7cjq-w44j-qx9w

Severity MODERATE

CVSS v3.1 Base Score 5.5

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-07-25

Last Updated 2026-09-04

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-64359

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-64359, 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: nilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers Syzbot reported a hung task in nilfs_transaction_begin() where multiple tasks performing chmod() on a nilfs2 mount blocked for over 143 seconds waiting to acquire ns_segctor_sem for read: INFO: task syz.0.17:5918 blocked for more than 143 seconds. Call Trace: schedule+0x164/0x360 rwsem_down_read_slowpath+0x6d9/0x940 down_read+0x99/0x2e0 nilfs_transaction_begin+0x364/0x710 fs/nilfs2/segment.c:221 nilfs_setattr+0x124/0x2c0 fs/nilfs2/inode.c:921 notify_change+0xc1a/0xf40 chmod_common+0x273/0x4a0 do_fchmodat+0x12d/0x230 The writer holding ns_segctor_sem was a concurrent NILFS_IOCTL_CLEAN_SEGMENTS caller, stuck inside printk while emitting per-element warnings from nilfs_sufile_updatev(): __nilfs_msg+0x373/0x450 fs/nilfs2/super.c:78 nilfs_sufile_updatev+0x21c/0x6d0 fs/nilfs2/sufile.c:186 nilfs_sufile_freev fs/nilfs2/sufile.h:93 [inline] nilfs_free_segments fs/nilfs2/segment.c:1140 [inline] nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1261 [inline] nilfs_segctor_do_construct+0x1f55/0x76c0 nilfs_clean_segments+0x3bd/0xa50 nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:922 [inline] nilfs_ioctl+0x261f/0x2780 The root cause is that user-supplied segment numbers are not validated before nilfs_clean_segments() begins doing work; the range check on each segnum is performed deep inside the call chain by nilfs_sufile_updatev(), which emits a nilfs_warn() per invalid entry while still holding the segctor lock and the sufile mi_sem. Under load (repeated invocations across multiple mounts saturating the global printk path), the cumulative printk latency keeps ns_segctor_sem held long enough to trip the hung_task watchdog, blocking concurrent operations such as chmod() that need ns_segctor_sem for read. Fix by validating the contents of kbufs[4] in nilfs_clean_segments() immediately after acquiring ns_segctor_sem via nilfs_transaction_lock(). Holding ns_segctor_sem serializes the check against nilfs_ioctl_resize(), which can modify ns_nsegments, so the validation uses a consistent value. Out-of-range segment numbers are rejected with -EINVAL before any segment-cleaning work begins, so the bad entries never reach the per-element diagnostic path inside nilfs_sufile_updatev().

References

NVD — CVE-2026-64359 NVD

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

git.kernel.org/stable/c/0789f0a671... WEB

https://git.kernel.org/stable/c/0789f0a6710713254a08f3a7d2ecbb6d1cbcf0aa

git.kernel.org/stable/c/0e7a690fe4... WEB

https://git.kernel.org/stable/c/0e7a690fe435f8d5ea3feb7c1d8d73ba7e8b8aa9

git.kernel.org/stable/c/223463c488... WEB

https://git.kernel.org/stable/c/223463c488b0554212a94de971ea538eb2805fc7

git.kernel.org/stable/c/286f77d002... WEB

https://git.kernel.org/stable/c/286f77d002a337735c0846d7480a82d9cda2aa31

git.kernel.org/stable/c/39607452b1... WEB

https://git.kernel.org/stable/c/39607452b1400c7bf748f15122df4d058b768c5b

git.kernel.org/stable/c/3ed388ec3b... WEB

https://git.kernel.org/stable/c/3ed388ec3b8922383d1e2d4432d7bd4cbbf8364e

git.kernel.org/stable/c/876c98e0fc... WEB

https://git.kernel.org/stable/c/876c98e0fc65f071680c03c2e2ee3ef7ff9ca078

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

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

Frequently Asked Questions

What is CVE-2026-64359?

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

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-64359?

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

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

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

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-7cjq-w44j-qx9w",
  "modified" : "2026-09-04T18:31:11Z",
  "published" : "2026-07-25T12:31:32Z",
  "aliases" : [ "CVE-2026-64359" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers\n\nSyzbot reported a hung task in nilfs_transaction_begin() where multiple\ntasks performing chmod() on a nilfs2 mount blocked for over 143 seconds\nwaiting to acquire ns_segctor_sem for read:\n\n  INFO: task syz.0.17:5918 blocked for more than 143 seconds.\n  Call Trace:\n   schedule+0x164/0x360\n   rwsem_down_read_slowpath+0x6d9/0x940\n   down_read+0x99/0x2e0\n   nilfs_transaction_begin+0x364/0x710 fs/nilfs2/segment.c:221\n   nilfs_setattr+0x124/0x2c0 fs/nilfs2/inode.c:921\n   notify_change+0xc1a/0xf40\n   chmod_common+0x273/0x4a0\n   do_fchmodat+0x12d/0x230\n\nThe writer holding ns_segctor_sem was a concurrent\nNILFS_IOCTL_CLEAN_SEGMENTS caller, stuck inside printk while emitting\nper-element warnings from nilfs_sufile_updatev():\n\n   __nilfs_msg+0x373/0x450 fs/nilfs2/super.c:78\n   nilfs_sufile_updatev+0x21c/0x6d0 fs/nilfs2/sufile.c:186\n   nilfs_sufile_freev fs/nilfs2/sufile.h:93 [inline]\n   nilfs_free_segments fs/nilfs2/segment.c:1140 [inline]\n   nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1261 [inline]\n   nilfs_segctor_do_construct+0x1f55/0x76c0\n   nilfs_clean_segments+0x3bd/0xa50\n   nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:922 [inline]\n   nilfs_ioctl+0x261f/0x2780\n\nThe root cause is that user-supplied segment numbers are not validated\nbefore nilfs_clean_segments() begins doing work; the range check on\neach segnum is performed deep inside the call chain by\nnilfs_sufile_updatev(), which emits a nilfs_warn() per invalid entry\nwhile still holding the segctor lock and the sufile mi_sem.  Under load\n(repeated invocations across multiple mounts saturating the global\nprintk path), the cumulative printk latency keeps ns_segctor_sem held\nlong enough to trip the hung_task watchdog, blocking concurrent\noperations such as chmod() that need ns_segctor_sem for read.\n\nFix by validating the contents of kbufs[4] in nilfs_clean_segments()\nimmediately after acquiring ns_segctor_sem via nilfs_transaction_lock().\nHolding ns_segctor_sem serializes the check against\nnilfs_ioctl_resize(), which can modify ns_nsegments, so the validation\nuses a consistent value.  Out-of-range segment numbers are rejected\nwith -EINVAL before any segment-cleaning work begins, so the bad\nentries never reach the per-element diagnostic path inside\nnilfs_sufile_updatev().",
  "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-64359"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0789f0a6710713254a08f3a7d2ecbb6d1cbcf0aa"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0e7a690fe435f8d5ea3feb7c1d8d73ba7e8b8aa9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/223463c488b0554212a94de971ea538eb2805fc7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/286f77d002a337735c0846d7480a82d9cda2aa31"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/39607452b1400c7bf748f15122df4d058b768c5b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3ed388ec3b8922383d1e2d4432d7bd4cbbf8364e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/876c98e0fc65f071680c03c2e2ee3ef7ff9ca078"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d26aef771b4f6923da9f89d6d5b70d8def5853de"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-25T10:17:18Z"
  }
}

CVSS V3

5.5 MODERATE