Skip to content
Threat Brief

← All advisories

CVE-2026-99461

Severity unknownNo known exploitationFix available

mm: khugepaged: fix swap entry value to folio_pfn()

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom d41fd2016ed07a630da2817b76c98eeab7931e1e before c4252273ead984541eb9313667f2924f2ff8d0e0c4252273ead984541eb9313667f2924f2ff8d0e0CVE Program
LinuxLinuxfrom d41fd2016ed07a630da2817b76c98eeab7931e1e before 9efc8d0c9c81094cfa99667154f5682d487e9b639efc8d0c9c81094cfa99667154f5682d487e9b63CVE Program
LinuxLinuxfrom d41fd2016ed07a630da2817b76c98eeab7931e1e before 942c8ec27aa4ffc587511650718349964e1696e6942c8ec27aa4ffc587511650718349964e1696e6CVE Program
LinuxLinuxfrom d41fd2016ed07a630da2817b76c98eeab7931e1e before 384c524e066459c91a8750a055fe70d56b334437384c524e066459c91a8750a055fe70d56b334437CVE Program
LinuxLinux6.1Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.63 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.1Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references