mm: khugepaged: fix swap entry value to folio_pfn()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c4252273ead984541eb9313667f2924f2ff8d0e0, Kernel 384c524e066459c91a8750a055fe70d56b334437, Kernel 942c8ec27aa4ffc587511650718349964e1696e6 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: mm: khugepaged: fix swap entry value to folio_pfn() Patch series "mm: khugepaged: fix tracepoint UAF", v5. The khugepaged tracepoints take a folio pointer and call folio_pfn(), but by then the folio may no longer be valid: freed after folio_put(), folio_unlock() or pte_unmap_unlock(), or not a folio at all but an xarray-encoded swap entry. On classic SPARSEMEM, dereferencing it oopses khugepaged as soon as the trace event is enabled; on other memory models it merely prints a bogus pfn. Pass the pfn to the tracepoints directly, captured while the folio is still pinned, closing the use-after-free windows in mm_khugepaged_scan_file(), mm_khugepaged_scan_pmd() and mm_khugepaged_collapse_file(). This patch (of 3): When the swap entries found exceed max_ptes_swap, the loop is left via break with folio still holding the xarray value that encodes the swap entry, not valid folio pointer. That value is passed to trace_mm_khugepaged_scan_file(), which feeds it to folio_pfn(). On FLATMEM and SPARSEMEM_VMEMMAP, the page_to_pfn() is plain pointer arithmetic, so the trace event merely prints bogus scan_pfn. On classic SPARSEMEM, the page_to_pfn() reads page->flags, dereferencing the tiny encoded integer and oopsing khugepaged whenever the trace event is enabled. So when folio is the swap entry value, simply set pfn to -1, just like exhausted scan naturally. And the folio_put() has maybe dropped the last reference of folio. The trace_mm_khugepaged_scan_file() is left with a dangling folio pointer. so using the folio_pfn() before dropping the reference, closing use-after-free window.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=d41fd2016ed07a630da2817b76c98eeab7931e1e <c4252273ead984541eb9313667f2924f2ff8d0e0, >=d41fd2016ed07a630da2817b76c98eeab7931e1e <384c524e066459c91a8750a055fe70d56b334437, >=d41fd2016ed07a630da2817b76c98eeab7931e1e <942c8ec27aa4ffc587511650718349964e1696e6, >=d41fd2016ed07a630da2817b76c98eeab7931e1e <9efc8d0c9c81094cfa99667154f5682d487e9b63, =6.1 | c4252273ead984541eb9313667f2924f2ff8d0e0, 384c524e066459c91a8750a055fe70d56b334437, 942c8ec27aa4ffc587511650718349964e1696e6, 9efc8d0c9c81094cfa99667154f5682d487e9b63 |
| linux-kernel: Kernel | >=6.13.0 <6.18.63, >=6.19.0 <7.3.2, >=6.1.0 <6.12.117 | 6.18.63, 7.3.2, 6.12.117 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket