mm: fix deadlock of mremap() against UFFDIO_MOVE
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3627d4eaa7f4426b979d497544ce23cb8884134b, Kernel d03df42ddae196f20e9cfb775704e60269eb6b44 and Kernel 7.3.5.
In the Linux kernel, the following vulnerability has been resolved: mm: fix deadlock of mremap() against UFFDIO_MOVE With per-VMA locks, UFFDIO_MOVE can run concurrently with mremap() on different VMAs in the same mm. Those VMAs can share page tables, so both operations can acquire the same pair of page-table locks. UFFDIO_MOVE orders the locks by address, while mremap() takes the source lock first. These conflicting orders can deadlock; mremap() holding mmap_lock for writing no longer helps. Move double_pt_lock() and double_pt_unlock() to mm/internal.h and use them for all page-table moves in mremap(). Preserve the source entry checks after acquiring both locks. Remove the comments claiming that exclusive mmap_lock makes lock ordering irrelevant. In move_ptes(), make sure to just recheck source and destination PMD after taking the locks and drop the overly-long comment. Fix generated by an LLM and sent by Chris Mason in private. [ david: use new helpers consistently; simplify description and comments; move_ptes() fixup ]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=867a43a34ff8a38772212045262b2c9b77807ea3 <3627d4eaa7f4426b979d497544ce23cb8884134b, >=867a43a34ff8a38772212045262b2c9b77807ea3 <d03df42ddae196f20e9cfb775704e60269eb6b44 | 3627d4eaa7f4426b979d497544ce23cb8884134b, d03df42ddae196f20e9cfb775704e60269eb6b44 |
| linux-kernel: Kernel | >=6.9.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