CVE-2026-72174

published 15 Aug 2026 · updated 15 Nov 2026

fs/proc/task_mmu: fix hugetlb self-deadlock in pagemap_scan_pte_hole()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e92d92bbafb264dc0518d52b846a3c07ed8d523f, Kernel 18b8a9700610299819d21fd0ea85d24726d17f65, Kernel 43b987ed35be9be21a303d1036d4241fec9943df and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=52526ca7fdb905a768a93f8faa418e9b988fc34b <e92d92bbafb264dc0518d52b846a3c07ed8d523f, >=52526ca7fdb905a768a93f8faa418e9b988fc34b <18b8a9700610299819d21fd0ea85d24726d17f65, >=52526ca7fdb905a768a93f8faa418e9b988fc34b <43b987ed35be9be21a303d1036d4241fec9943df, >=52526ca7fdb905a768a93f8faa418e9b988fc34b <a6ac03652d9edc30c2912037ac83beb42cc67f8e, =6.7e92d92bbafb264dc0518d52b846a3c07ed8d523f, 18b8a9700610299819d21fd0ea85d24726d17f65, 43b987ed35be9be21a303d1036d4241fec9943df, a6ac03652d9edc30c2912037ac83beb42cc67f8e
linux-kernel: Kernel>=6.19.0 <7.1.5, >=6.7.0 <6.12.97, >=6.13.0 <6.18.407.1.5, 6.12.97, 6.18.40

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-72174 severity on Zeptric[![CVE-2026-72174](https://zeptric.io/badge/cve/CVE-2026-72174.svg)](https://zeptric.io/cve/CVE-2026-72174)