Skip to main content
VulnerabilityPublished

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c4252273ead984541eb9313667f2924f2ff8d0e0 : update Linux kernel when convenient.

Data as of 19 Nov 2026, 14:49 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in c4252273ead984541eb9313667f2924f2ff8d0e0, 942c8ec27aa4ffc587511650718349964e1696e6, 384c524e066459c91a8750a055fe70d56b334437 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to c4252273ead984541eb9313667f2924f2ff8d0e0, 942c8ec27aa4ffc587511650718349964e1696e6, 384c524e066459c91a8750a055fe70d56b334437 or 9efc8d0c9c81094cfa99667154f5682d487e9b63.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ d41fd2016ed07a630da2817b76c98eeab7931e1e, < c4252273ead984541eb9313667f2924f2ff8d0e0
Fixed in
  • c4252273ead984541eb9313667f2924f2ff8d0e0
LinuxLinuxAffected
  • ≥ d41fd2016ed07a630da2817b76c98eeab7931e1e, < 942c8ec27aa4ffc587511650718349964e1696e6
Fixed in
  • 942c8ec27aa4ffc587511650718349964e1696e6
LinuxLinuxAffected
  • ≥ d41fd2016ed07a630da2817b76c98eeab7931e1e, < 384c524e066459c91a8750a055fe70d56b334437
Fixed in
  • 384c524e066459c91a8750a055fe70d56b334437
LinuxLinuxAffected
  • ≥ d41fd2016ed07a630da2817b76c98eeab7931e1e, < 9efc8d0c9c81094cfa99667154f5682d487e9b63
Fixed in
  • 9efc8d0c9c81094cfa99667154f5682d487e9b63
LinuxLinuxAffected
  • =6.1
Fixed in–

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.

References

Community reviews

Loading reviews…