CVE-2026-72174: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-xxr9-w8rg-g2h6
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-72174
GHSA Identifier GHSA-xxr9-w8rg-g2h6
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-72174

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-72174, 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: fs/proc/task_mmu: fix hugetlb self-deadlock in pagemap_scan_pte_hole() A PAGEMAP_SCAN ioctl requesting PM_SCAN_WP_MATCHING on a hugetlb VMA hangs the calling thread, unkillably, as soon as the scan reaches an unpopulated part of the range: do_pagemap_scan() walk_page_range() walk_hugetlb_range() hugetlb_vma_lock_read() # take the vma lock for read ... pagemap_scan_pte_hole() # ... ->pte_hole() for a hole uffd_wp_range() change_protection() hugetlb_change_protection() hugetlb_vma_lock_write() # ... and block taking it for write walk_hugetlb_range() holds the hugetlb vma lock for read across the whole walk. A present entry goes to ->hugetlb_entry(); an unpopulated one goes to ->pte_hole(), i.e. pagemap_scan_pte_hole(). To write-protect the hole that handler calls uffd_wp_range(), which on a hugetlb VMA reaches hugetlb_change_protection() and takes the same vma lock for write. The thread then blocks in down_write() waiting for the read lock it is itself holding. The populated path avoids this: pagemap_scan_hugetlb_entry() write-protects the entry inline under the page-table lock and never enters hugetlb_change_protection(). Do the same for holes. Fault in the page table and install the uffd-wp marker directly with make_uffd_wp_huge_pte() under the page-table lock, rather than routing through uffd_wp_range(). That is the same sequence hugetlb_change_protection() runs for an unpopulated entry, minus the vma write lock -- which is safe to skip because PMD sharing is disabled on uffd-wp VMAs (hugetlb_unshare_all_pmds() runs at registration), leaving nothing for that lock to serialise against.

References

NVD — CVE-2026-72174 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72174
git.kernel.org/stable/c/18b8a97006... WEB
https://git.kernel.org/stable/c/18b8a9700610299819d21fd0ea85d24726d17f65
git.kernel.org/stable/c/43b987ed35... WEB
https://git.kernel.org/stable/c/43b987ed35be9be21a303d1036d4241fec9943df
git.kernel.org/stable/c/a6ac03652d... WEB
https://git.kernel.org/stable/c/a6ac03652d9edc30c2912037ac83beb42cc67f8e
git.kernel.org/stable/c/e92d92bbaf... WEB
https://git.kernel.org/stable/c/e92d92bbafb264dc0518d52b846a3c07ed8d523f

Frequently Asked Questions

What is CVE-2026-72174?
CVE-2026-72174 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-72174?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-72174?
CVE-2026-72174 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72174?
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-xxr9-w8rg-g2h6",
  "modified" : "2026-08-15T06:32:14Z",
  "published" : "2026-08-15T06:32:14Z",
  "aliases" : [ "CVE-2026-72174" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc/task_mmu: fix hugetlb self-deadlock in pagemap_scan_pte_hole()\n\nA PAGEMAP_SCAN ioctl requesting PM_SCAN_WP_MATCHING on a hugetlb VMA hangs\nthe calling thread, unkillably, as soon as the scan reaches an unpopulated\npart of the range:\n\n  do_pagemap_scan()\n    walk_page_range()\n      walk_hugetlb_range()\n        hugetlb_vma_lock_read()           # take the vma lock for read ...\n        pagemap_scan_pte_hole()           # ... ->pte_hole() for a hole\n          uffd_wp_range()\n            change_protection()\n              hugetlb_change_protection()\n                hugetlb_vma_lock_write()  # ... and block taking it for write\n\nwalk_hugetlb_range() holds the hugetlb vma lock for read across the whole\nwalk.  A present entry goes to ->hugetlb_entry(); an unpopulated one goes\nto ->pte_hole(), i.e.  pagemap_scan_pte_hole().  To write-protect the hole\nthat handler calls uffd_wp_range(), which on a hugetlb VMA reaches\nhugetlb_change_protection() and takes the same vma lock for write.  The\nthread then blocks in down_write() waiting for the read lock it is itself\nholding.\n\nThe populated path avoids this: pagemap_scan_hugetlb_entry()\nwrite-protects the entry inline under the page-table lock and never enters\nhugetlb_change_protection().\n\nDo the same for holes.  Fault in the page table and install the uffd-wp\nmarker directly with make_uffd_wp_huge_pte() under the page-table lock,\nrather than routing through uffd_wp_range().  That is the same sequence\nhugetlb_change_protection() runs for an unpopulated entry, minus the vma\nwrite lock -- which is safe to skip because PMD sharing is disabled on\nuffd-wp VMAs (hugetlb_unshare_all_pmds() runs at registration), leaving\nnothing for that lock to serialise against.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72174"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/18b8a9700610299819d21fd0ea85d24726d17f65"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/43b987ed35be9be21a303d1036d4241fec9943df"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a6ac03652d9edc30c2912037ac83beb42cc67f8e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e92d92bbafb264dc0518d52b846a3c07ed8d523f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:35Z"
  }
}