mm: clear uffd-wp PTE/PMD state on mremap()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0cef0bb836e3cfe00f08f9606c72abd72fe78ca3, Kernel 310ac886d68de661c3a334198d8604b722d7fdf8, Kernel 8e2f6ba256dd1e590addc48e6e9577bf39c482f2 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: mm: clear uffd-wp PTE/PMD state on mremap() When mremap()ing a memory region previously registered with userfaultfd as write-protected but without UFFD_FEATURE_EVENT_REMAP, an inconsistency in flag clearing leads to a mismatch between the vma flags (which have uffd-wp cleared) and the pte/pmd flags (which do not have uffd-wp cleared). This mismatch causes a subsequent mprotect(PROT_WRITE) to trigger a warning in page_table_check_pte_flags() due to setting the pte to writable while uffd-wp is still set. Fix this by always explicitly clearing the uffd-wp pte/pmd flags on any such mremap() so that the values are consistent with the existing clearing of VM_UFFD_WP. Be careful to clear the logical flag regardless of its physical form; a PTE bit, a swap PTE bit, or a PTE marker. Cover PTE, huge PMD and hugetlb paths.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.7, >=63b2d4174c4ad1f40b48d7138e71bcb564c1fe03 <0cef0bb836e3cfe00f08f9606c72abd72fe78ca3, >=63b2d4174c4ad1f40b48d7138e71bcb564c1fe03 <310ac886d68de661c3a334198d8604b722d7fdf8, >=63b2d4174c4ad1f40b48d7138e71bcb564c1fe03 <8e2f6ba256dd1e590addc48e6e9577bf39c482f2, >=63b2d4174c4ad1f40b48d7138e71bcb564c1fe03 <96fed9f20481d07eba8a7fe93bc77abef178198c | 0cef0bb836e3cfe00f08f9606c72abd72fe78ca3, 310ac886d68de661c3a334198d8604b722d7fdf8, 8e2f6ba256dd1e590addc48e6e9577bf39c482f2, 96fed9f20481d07eba8a7fe93bc77abef178198c |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket