CVE-2026-72353: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-7mwr-cgqq-xj42
CVSS 8.8
Published
Advisory Summary

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

CVE-2026-72353 at a Glance

CVE Identifier CVE-2026-72353
GHSA Identifier GHSA-7mwr-cgqq-xj42
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.8

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

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

How to Fix CVE-2026-72353

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-72353, 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: ntfs: avoid stale runlist element dereference in fallocate ntfs_attr_fallocate() allocates holes and delayed allocations inside initialized size by looking up the current runlist element under ni->runlist.lock. The returned struct runlist_element is only a borrowed pointer into ni->runlist.rl. A writer can replace and free that array after the read lock is dropped, so later reads of rl->lcn, rl->length and rl->vcn can touch freed memory. The buggy scenario involves two paths, with each column showing the order within that path: ntfs_attr_fallocate(): 1. Take ni->runlist.lock for read. 2. Get rl from ntfs_attr_find_vcn_nolock(). 3. Drop ni->runlist.lock. 4. Read rl->lcn, rl->length and rl->vcn. mmap page_mkwrite: 1. Enter ntfs_filemap_page_mkwrite(). 2. Reach __ntfs_write_iomap_begin() and ntfs_attr_map_cluster(). 3. Merge allocation state with ntfs_runlists_merge(). 4. Reallocate ni->runlist.rl in ntfs_rl_realloc(), freeing the old array. Validation reproduced this kernel report: BUG: KASAN: slab-use-after-free in ntfs_attr_fallocate+0xbb8/0xd00 Call Trace: <TASK> dump_stack_lvl+0x66/0xa0 print_report+0xce/0x630 ? ntfs_attr_fallocate+0xbb8/0xd00 ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x20d/0x410 ? ntfs_attr_fallocate+0xbb8/0xd00 kasan_report+0xe0/0x110 ? ntfs_attr_fallocate+0xbb8/0xd00 ntfs_attr_fallocate+0xbb8/0xd00 ? lock_acquire+0x2b8/0x2f0 ? __pfx_ntfs_attr_fallocate+0x10/0x10 ? 0xffffffffc0000095 ? down_write+0x10d/0x1e0 ntfs_fallocate+0x5c9/0x1d00 ? __pfx_ntfs_fallocate+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? lock_acquire+0x2b8/0x2f0 ? srso_alias_return_thunk+0x5/0xfbef5 ? selinux_file_permission+0x3a7/0x510 vfs_fallocate+0x29d/0xd30 __x64_sys_fallocate+0xc7/0x150 ? do_syscall_64+0x81/0x6a0 do_syscall_64+0x115/0x6a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f Allocated by task 410: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 __kvmalloc_node_noprof+0x353/0x920 ntfs_rl_realloc+0x3f/0x110 ntfs_runlists_merge+0xaa3/0x3010 ntfs_attr_map_cluster+0x4e5/0xf80 ntfs_attr_fallocate+0x53f/0xd00 ntfs_fallocate+0x5c9/0x1d00 vfs_fallocate+0x29d/0xd30 __x64_sys_fallocate+0xc7/0x150 do_syscall_64+0x115/0x6a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 424: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x5f/0x80 kfree+0x307/0x580 ntfs_rl_realloc+0x6f/0x110 ntfs_runlists_merge+0x7b1/0x3010 ntfs_attr_map_cluster+0x4e5/0xf80 __ntfs_write_iomap_begin+0x8cd/0x2280 iomap_iter+0x6de/0x11e0 iomap_page_mkwrite+0x391/0x650 ntfs_filemap_page_mkwrite+0x1ac/0x400 do_page_mkwrite+0x15c/0x280 __handle_mm_fault+0xd6d/0x1ca0 handle_mm_fault+0x19c/0x470 do_user_addr_fault+0x23b/0x9c0 exc_page_fault+0x5c/0xc0 asm_exc_page_fault+0x26/0x30 Fix this by copying the needed runlist fields while the read lock is still held and using only those scalar snapshots after unlocking. After the snapshot, ntfs_attr_map_cluster() can also find that the range is already mapped and return balloc=false. Only call ntfs_dio_zero_range() when new clusters were allocated, matching the write iomap path and preserving the zero-newly-allocated-holes behavior.

References

Frequently Asked Questions

What is CVE-2026-72353?
CVE-2026-72353 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-72353?
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-72353?
CVE-2026-72353 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72353?
CVE-2026-72353 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72353?
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-7mwr-cgqq-xj42",
  "modified" : "2026-08-17T06:33:25Z",
  "published" : "2026-08-15T06:32:21Z",
  "aliases" : [ "CVE-2026-72353" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: avoid stale runlist element dereference in fallocate\n\nntfs_attr_fallocate() allocates holes and delayed allocations inside\ninitialized size by looking up the current runlist element under\nni->runlist.lock. The returned struct runlist_element is only a borrowed\npointer into ni->runlist.rl. A writer can replace and free that array\nafter the read lock is dropped, so later reads of rl->lcn, rl->length and\nrl->vcn can touch freed memory.\n\nThe buggy scenario involves two paths, with each column showing the order\nwithin that path:\n\nntfs_attr_fallocate():\n  1. Take ni->runlist.lock for read.\n  2. Get rl from ntfs_attr_find_vcn_nolock().\n  3. Drop ni->runlist.lock.\n  4. Read rl->lcn, rl->length and rl->vcn.\n\nmmap page_mkwrite:\n  1. Enter ntfs_filemap_page_mkwrite().\n  2. Reach __ntfs_write_iomap_begin() and ntfs_attr_map_cluster().\n  3. Merge allocation state with ntfs_runlists_merge().\n  4. Reallocate ni->runlist.rl in ntfs_rl_realloc(), freeing the old array.\n\nValidation reproduced this kernel report:\nBUG: KASAN: slab-use-after-free in ntfs_attr_fallocate+0xbb8/0xd00\n\nCall Trace:\n <TASK>\n dump_stack_lvl+0x66/0xa0\n print_report+0xce/0x630\n ? ntfs_attr_fallocate+0xbb8/0xd00\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? __virt_addr_valid+0x20d/0x410\n ? ntfs_attr_fallocate+0xbb8/0xd00\n kasan_report+0xe0/0x110\n ? ntfs_attr_fallocate+0xbb8/0xd00\n ntfs_attr_fallocate+0xbb8/0xd00\n ? lock_acquire+0x2b8/0x2f0\n ? __pfx_ntfs_attr_fallocate+0x10/0x10\n ? 0xffffffffc0000095\n ? down_write+0x10d/0x1e0\n ntfs_fallocate+0x5c9/0x1d00\n ? __pfx_ntfs_fallocate+0x10/0x10\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? lock_acquire+0x2b8/0x2f0\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? selinux_file_permission+0x3a7/0x510\n vfs_fallocate+0x29d/0xd30\n __x64_sys_fallocate+0xc7/0x150\n ? do_syscall_64+0x81/0x6a0\n do_syscall_64+0x115/0x6a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nAllocated by task 410:\n kasan_save_stack+0x33/0x60\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0xaa/0xb0\n __kvmalloc_node_noprof+0x353/0x920\n ntfs_rl_realloc+0x3f/0x110\n ntfs_runlists_merge+0xaa3/0x3010\n ntfs_attr_map_cluster+0x4e5/0xf80\n ntfs_attr_fallocate+0x53f/0xd00\n ntfs_fallocate+0x5c9/0x1d00\n vfs_fallocate+0x29d/0xd30\n __x64_sys_fallocate+0xc7/0x150\n do_syscall_64+0x115/0x6a0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 424:\n kasan_save_stack+0x33/0x60\n kasan_save_track+0x14/0x30\n kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x5f/0x80\n kfree+0x307/0x580\n ntfs_rl_realloc+0x6f/0x110\n ntfs_runlists_merge+0x7b1/0x3010\n ntfs_attr_map_cluster+0x4e5/0xf80\n __ntfs_write_iomap_begin+0x8cd/0x2280\n iomap_iter+0x6de/0x11e0\n iomap_page_mkwrite+0x391/0x650\n ntfs_filemap_page_mkwrite+0x1ac/0x400\n do_page_mkwrite+0x15c/0x280\n __handle_mm_fault+0xd6d/0x1ca0\n handle_mm_fault+0x19c/0x470\n do_user_addr_fault+0x23b/0x9c0\n exc_page_fault+0x5c/0xc0\n asm_exc_page_fault+0x26/0x30\n\nFix this by copying the needed runlist fields while the read lock is still\nheld and using only those scalar snapshots after unlocking.\n\nAfter the snapshot, ntfs_attr_map_cluster() can also find that the range\nis already mapped and return balloc=false. Only call ntfs_dio_zero_range()\nwhen new clusters were allocated, matching the write iomap path and\npreserving the zero-newly-allocated-holes behavior.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72353"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3dd3e43f17cda174009a51fe668046ed7afef46a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/88496c4ac5a6ade75619f4b1015706a8b924d50a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:08Z"
  }
}