CVE-2026-99461: mm: khugepaged: fix swap entry value to folio_pfn()

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

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

Patch series "mm: khugepaged: fix tracepoint UAF", v5.

The khugepaged tracepoints take a folio pointer and call foliopfn(), but by then the folio may no longer be valid: freed after folioput(), foliounlock() or pteunmapunlock(), 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 mmkhugepagedscanfile(), mmkhugepagedscanpmd() and mmkhugepagedcollapsefile().

This patch (of 3):

When the swap entries found exceed maxptesswap, 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 tracemmkhugepagedscanfile(), which feeds it to foliopfn(). On FLATMEM and SPARSEMEMVMEMMAP, the pagetopfn() is plain pointer arithmetic, so the trace event merely prints bogus scanpfn. On classic SPARSEMEM, the pagetopfn() 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 folioput() has maybe dropped the last reference of folio. The tracemmkhugepagedscanfile() is left with a dangling folio pointer. so using the foliopfn() before dropping the reference, closing use-after-free window.

Affected Software

7 affected componentsFixes available
linux/kernel>=6.1.0<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.63
6.18.63
linux/kernel>=6.19.0<7.3.2
7.3.2
debian/linux*
debian/linux<6.12.117-1
6.12.117-1
debian/linux<7.3.3-1
7.3.3-1
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1
6.12.117-17.3.4-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.63
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.117-1
  5. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.3-1
  6. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1

Event History

Nov 19, 2026
CVE Published
via MITRE·02:42 PM
Data Sourced
via MITRE·02:42 PM
Description
Data Sourced
via OSV·02:42 PM
DescriptionAffected Software
Data Sourced
via NVD·03:18 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203