mm/khugepaged: fix PMD table lock leak in try_collapse_pte_mapped_thp()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7c1170ce1b74a8cd83da2174a3eb9e0755bb1b16, Kernel ad5e5800ce560759c8d3c10aac15b48a06cd21c1, Kernel db38b902307e687219ec765ef51a6ef459746c87 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: fix PMD table lock leak in try_collapse_pte_mapped_thp() For a private mapping with userfaultfd, try_collapse_pte_mapped_thp() takes the PMD table lock before it maps the page table for the second time. If that (pte_offset_map_rw_nolock) fails, because the page table vanished in the meantime due to concurrent page table reclaim, it leaves through the abort label, where the PMD table lock is unlocked if it differs from PTE table lock. In case the PMD table lock and the PTE table lock match, which is the case without CONFIG_SPLIT_PTE_PTLOCKS after pte_offset_map_rw_nolock() failed, we miss to unlock the PMD table. To fix it, forget the PTE table lock when we unmap+unlock the PTE table. Fix generated by an LLM and sent by Josef Bacik in private. [ david: move the ptl = NULL handling; rewrite description, drop wrong comments ]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.14, >=6375e95f381e3dc85065b6f74263a61522736203 <7c1170ce1b74a8cd83da2174a3eb9e0755bb1b16, >=6375e95f381e3dc85065b6f74263a61522736203 <ad5e5800ce560759c8d3c10aac15b48a06cd21c1, >=6375e95f381e3dc85065b6f74263a61522736203 <db38b902307e687219ec765ef51a6ef459746c87 | 7c1170ce1b74a8cd83da2174a3eb9e0755bb1b16, ad5e5800ce560759c8d3c10aac15b48a06cd21c1, db38b902307e687219ec765ef51a6ef459746c87 |
| linux-kernel: Kernel | >=6.14.0 <6.18.64, >=6.19.0 <7.3.5 | 6.18.64, 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