CVE-2026-74307: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-j6rh-x9jg-pr3v
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-74307
GHSA Identifier GHSA-j6rh-x9jg-pr3v
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-74307

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-74307, 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: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT Reject the EXT4_IOC_MOVE_EXT ioctl early if the donor file does not belong to the same superblock as the original file. Currently, this validation is performed inside ext4_move_extents() by mext_check_validity(), but only after lock_two_nondirectories() has already acquired the inode locks. When the donor fd refers to a file on a different filesystem (e.g., overlayfs), this late validation creates a circular lock dependency: CPU0 (overlayfs write) CPU1 (ext4 ioctl) ---- ---- inode_lock(ovl_inode) mnt_want_write_file(filp) sb_start_write(ext4_sb) [sb_writers] backing_file_write_iter() vfs_iter_write(real_file) file_start_write(real_file) sb_start_write(ext4_sb) [blocked by freeze] lock_two_nondirectories() inode_lock(ovl_inode) [blocked] With a concurrent freeze operation holding sb_writers write side, this forms a deadlock cycle: CPU0 waits for freeze to complete, freeze waits for CPU1's sb_writers reader to exit, CPU1 waits for CPU0's inode lock. Since EXT4_IOC_MOVE_EXT exchanges physical extents between two files, it fundamentally requires both files to reside on the same ext4 filesystem. Moving the superblock check before any lock acquisition is both semantically correct and eliminates the circular dependency by ensuring that cross-filesystem donor fds are rejected before sb_writers or inode locks are taken.

References

NVD — CVE-2026-74307 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74307
git.kernel.org/stable/c/29e07ec352... WEB
https://git.kernel.org/stable/c/29e07ec352f0ad06c833a18bf47d82c81f55544f
git.kernel.org/stable/c/74796e886c... WEB
https://git.kernel.org/stable/c/74796e886ca39fcb0d3fd36ea6a39c62784ab6fb
git.kernel.org/stable/c/c143957520... WEB
https://git.kernel.org/stable/c/c143957520c6c9b5cd72e0de8b52b814f0c576fe
git.kernel.org/stable/c/fb52013cad... WEB
https://git.kernel.org/stable/c/fb52013cad9e9b7d3a6a14ea1bcd841e41da7c6c

Frequently Asked Questions

What is CVE-2026-74307?
CVE-2026-74307 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-74307?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-74307?
CVE-2026-74307 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74307?
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-j6rh-x9jg-pr3v",
  "modified" : "2026-10-15T12:30:42Z",
  "published" : "2026-08-15T06:32:28Z",
  "aliases" : [ "CVE-2026-74307" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\next4: validate donor file superblock early in EXT4_IOC_MOVE_EXT\n\nReject the EXT4_IOC_MOVE_EXT ioctl early if the donor file does not\nbelong to the same superblock as the original file.  Currently, this\nvalidation is performed inside ext4_move_extents() by\nmext_check_validity(), but only after lock_two_nondirectories() has\nalready acquired the inode locks.  When the donor fd refers to a file\non a different filesystem (e.g., overlayfs), this late validation\ncreates a circular lock dependency:\n\n  CPU0 (overlayfs write)            CPU1 (ext4 ioctl)\n  ----                              ----\n  inode_lock(ovl_inode)\n                                    mnt_want_write_file(filp)\n                                      sb_start_write(ext4_sb)   [sb_writers]\n    backing_file_write_iter()\n      vfs_iter_write(real_file)\n        file_start_write(real_file)\n          sb_start_write(ext4_sb)   [blocked by freeze]\n                                    lock_two_nondirectories()\n                                      inode_lock(ovl_inode)     [blocked]\n\nWith a concurrent freeze operation holding sb_writers write side, this\nforms a deadlock cycle: CPU0 waits for freeze to complete, freeze waits\nfor CPU1's sb_writers reader to exit, CPU1 waits for CPU0's inode lock.\n\nSince EXT4_IOC_MOVE_EXT exchanges physical extents between two files,\nit fundamentally requires both files to reside on the same ext4\nfilesystem.  Moving the superblock check before any lock acquisition\nis both semantically correct and eliminates the circular dependency\nby ensuring that cross-filesystem donor fds are rejected before\nsb_writers or inode locks are taken.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74307"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/29e07ec352f0ad06c833a18bf47d82c81f55544f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/74796e886ca39fcb0d3fd36ea6a39c62784ab6fb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c143957520c6c9b5cd72e0de8b52b814f0c576fe"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fb52013cad9e9b7d3a6a14ea1bcd841e41da7c6c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:30Z"
  }
}