mm/hugetlb: do not call vma_add_reservation upon ENOMEM
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8daf9c702ee7f825f0de8600abff764acfedea13 and Kernel aa998f9dcb34c28448f86e8f5490f20d5eb0eac7.
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: do not call vma_add_reservation upon ENOMEM sysbot reported a splat [1] on __unmap_hugepage_range(). This is because vma_needs_reservation() can return -ENOMEM if allocate_file_region_entries() fails to allocate the file_region struct for the reservation. Check for that and do not call vma_add_reservation() if that is the case, otherwise region_abort() and region_del() will see that we do not have any file_regions. If we detect that vma_needs_reservation() returned -ENOMEM, we clear the hugetlb_restore_reserve flag as if this reservation was still consumed, so free_huge_folio() will not increment the resv count. [1] https://lore.kernel.org/linux-mm/0000000000004096100617c58d54@google.com/T/#ma5983bc1ab18a54910da83416b3f89f3c7ee43aa
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=df7a6d1f64056aec572162c5d35ed9ff86ece6f3 <8daf9c702ee7f825f0de8600abff764acfedea13, >=df7a6d1f64056aec572162c5d35ed9ff86ece6f3 <aa998f9dcb34c28448f86e8f5490f20d5eb0eac7 | 8daf9c702ee7f825f0de8600abff764acfedea13, aa998f9dcb34c28448f86e8f5490f20d5eb0eac7 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket