mm/huge_memory: properly handle refcounted PUD mappings on fork
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d90bdc02e36ec08d8248ebc6cdc52e12043eb28c, Kernel e8ebc5a46795cd1fb4333df81f19bbf458467cce and Kernel 7.3.5.
In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: properly handle refcounted PUD mappings on fork copy_huge_pud() copies device-DAX entries without taking a folio reference or updating mapcounts and the child's RSS. For example, MADV_GUARD_INSTALL sets VM_MAYBE_GUARD on a device-DAX VMA, forcing copy_page_range() to traverse the whole VMA on fork. Any remaining huge PUDs are then copied without accounting for the new mappings. Unmapping them in the child decrements accounting that was never added. Use vm_normal_page_pud() to identify refcounted mappings. Take a folio reference and add the child's PUD rmap and RSS accounting before installing the copied entry. Pass src and dst VMAs consistently instead of src and dst MM. Move the TODO.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.15, >=aed877c2b4257a25b2429f165542f86125871071 <d90bdc02e36ec08d8248ebc6cdc52e12043eb28c, >=aed877c2b4257a25b2429f165542f86125871071 <e8ebc5a46795cd1fb4333df81f19bbf458467cce | d90bdc02e36ec08d8248ebc6cdc52e12043eb28c, e8ebc5a46795cd1fb4333df81f19bbf458467cce |
| linux-kernel: Kernel | >=6.15.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket