{"id":"CVE-2026-99461","summary":"mm: khugepaged: fix swap entry value to folio_pfn()","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm: khugepaged: fix swap entry value to folio_pfn()\n\nPatch series \"mm: khugepaged: fix tracepoint UAF\", v5.\n\nThe khugepaged tracepoints take a folio pointer and call folio_pfn(), but\nby then the folio may no longer be valid: freed after folio_put(),\nfolio_unlock() or pte_unmap_unlock(), or not a folio at all but an\nxarray-encoded swap entry.  On classic SPARSEMEM, dereferencing it oopses\nkhugepaged as soon as the trace event is enabled; on other memory models\nit merely prints a bogus pfn.\n\nPass the pfn to the tracepoints directly, captured while the folio is\nstill pinned, closing the use-after-free windows in\nmm_khugepaged_scan_file(), mm_khugepaged_scan_pmd() and\nmm_khugepaged_collapse_file().\n\n\nThis patch (of 3):\n\nWhen the swap entries found exceed max_ptes_swap, the loop is left via\nbreak with folio still holding the xarray value that encodes the swap\nentry, not valid folio pointer.\n\nThat value is passed to trace_mm_khugepaged_scan_file(), which feeds it to\nfolio_pfn().  On FLATMEM and SPARSEMEM_VMEMMAP, the page_to_pfn() is plain\npointer arithmetic, so the trace event merely prints bogus scan_pfn.  On\nclassic SPARSEMEM, the page_to_pfn() reads page-\u003eflags, dereferencing the\ntiny encoded integer and oopsing khugepaged whenever the trace event is\nenabled.\n\nSo when folio is the swap entry value, simply set pfn to -1, just like\nexhausted scan naturally.\n\nAnd the folio_put() has maybe dropped the last reference of folio.  The\ntrace_mm_khugepaged_scan_file() is left with a dangling folio pointer.  so\nusing the folio_pfn() before dropping the reference, closing\nuse-after-free window.","modified":"2026-11-19T17:01:20.497292449Z","published":"2026-11-19T14:42:08.945Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99461.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/384c524e066459c91a8750a055fe70d56b334437"},{"type":"WEB","url":"https://git.kernel.org/stable/c/942c8ec27aa4ffc587511650718349964e1696e6"},{"type":"WEB","url":"https://git.kernel.org/stable/c/9efc8d0c9c81094cfa99667154f5682d487e9b63"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c4252273ead984541eb9313667f2924f2ff8d0e0"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99461.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99461"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"d41fd2016ed07a630da2817b76c98eeab7931e1e"},{"fixed":"384c524e066459c91a8750a055fe70d56b334437"},{"fixed":"c4252273ead984541eb9313667f2924f2ff8d0e0"},{"fixed":"9efc8d0c9c81094cfa99667154f5682d487e9b63"},{"fixed":"942c8ec27aa4ffc587511650718349964e1696e6"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99461.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.0"},{"fixed":"6.12.117"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.63"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.2"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99461.json"}}],"schema_version":"1.9.2"}