Linux kernel use-after-free in khugepaged tracepoints
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
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.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99461 (mm: khugepaged: fix swap entry value to folio_pfn()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99461 (entry last updated 2026-11-19):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 6.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99461 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99461 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/384c524e066459c91a8750a055fe70d56b334437
- https://git.kernel.org/stable/c/c4252273ead984541eb9313667f2924f2ff8d0e0
- https://git.kernel.org/stable/c/9efc8d0c9c81094cfa99667154f5682d487e9b63
- https://git.kernel.org/stable/c/942c8ec27aa4ffc587511650718349964e1696e6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99461
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99461"}.Affected versions
- Linux LinuxVersion range not reported
- Linux Linux6.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99461 |
| Record | NVD · CVE-2026-99461 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/384c524e066459c91a8750a055fe70d56b334437 |
| Link | git.kernel.org · stable/c/c4252273ead984541eb9313667f2924f2ff8d0e0 |
| Link | git.kernel.org · stable/c/9efc8d0c9c81094cfa99667154f5682d487e9b63 |
| Link | git.kernel.org · stable/c/942c8ec27aa4ffc587511650718349964e1696e6 |
Questions about CVE-2026-99461
Is CVE-2026-99461 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99461?
Linux: version 6.1.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.