mm/userfaultfd: fix hugetlb fault mutex hash calculation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mm/userfaultfd: fix hugetlb fault mutex hash calculation
In mfill_atomic_hugetlb(), linear_page_index() is used to calculate the page index for hugetlb_fault_mutex_hash(). However, linear_page_index() returns the index in PAGE_SIZE units, while hugetlb_fault_mutex_hash() expects the index in huge page units. This mismatch means that different addresses within the same huge page can produce different hash values, leading to the use of different mutexes for the same huge page. This can cause races between faulting threads, which can corrupt the reservation map and trigger the BUG_ON in resv_map_release().
Fix this by introducing hugetlb_linear_page_index(), which returns the page index in huge page granularity, and using it in place of linear_page_index().
From the CVE record · Linux
The Linux kernel’s hugetlb userfaultfd path can use different mutexes for addresses within the same huge page. Concurrent faulting threads can then race, corrupt the reservation map, and trigger a kernel BUG_ON. The input does not specify authentication requirements or whether user interaction is needed.
Engineers running Linux kernels with the affected hugetlb userfaultfd code should check their kernel versions; affected versions were not provided.