mm/huge_memory: split huge PUDs when adjusting VMA boundaries
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel bd918ee291da2d76dd03b5f9c2c2e550095ab538, Kernel 23e570927421d569fdc510d5f3f29542a43eeda5, Kernel 4636bc02303032f20710d97f40adb8f4eed22a66 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: split huge PUDs when adjusting VMA boundaries PFN mappings such as VFIO PCI BAR mappings can use PUD leaves while allowing VMA splits at page granularity. However, vma_adjust_trans_huge() only handles PMDs. After faulting a writable PUD-sized VFIO BAR mapping, changing its first page to read-only with mprotect() makes the PMD walk treat the PUD leaf as a PMD table. Applying MADV_DONTFORK to the first PMD-sized chunk leaves the PUD spanning two VMAs: the PMD-aligned boundary skips splitting. Walk the page tables once at each adjusted boundary and split a huge PUD or PMD leaf as needed. Handle PUD leaves even when the boundary is PMD-aligned.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101 <bd918ee291da2d76dd03b5f9c2c2e550095ab538, >=f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101 <23e570927421d569fdc510d5f3f29542a43eeda5, >=f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101 <4636bc02303032f20710d97f40adb8f4eed22a66, >=f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101 <605ebb555bc8695b309dcd462be6c1437ef98421, =6.12 | bd918ee291da2d76dd03b5f9c2c2e550095ab538, 23e570927421d569fdc510d5f3f29542a43eeda5, 4636bc02303032f20710d97f40adb8f4eed22a66, 605ebb555bc8695b309dcd462be6c1437ef98421 |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=6.12.0 <6.12.118 | 6.18.64, 7.3.5, 6.12.118 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket