CVE Professor
›
Back
CVE-2026-99461

CVE-2026-99461 — NONE Vulnerability

NONE CVSS 0 NVD

CVE-2026-99461 is a NONE severity security vulnerability (CVSS 0.0/10) affecting affected software system. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), posing a direct security risk to affected deployments.

📄 Official NVD / MITRE Original Record Text

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.

Published 19.11.2026
ISO Date 2026-11-19
Source NVD
AI Security Analysis & Remediation
🤖 Generating Deep AI Security Analysis…
Analyzing CVSS vector & CWE weakness structure…

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-99461
CVSS 0/10 · UNKNOWN · 19.11.2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 WHAT IS THIS VULNERABILITY?
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-encod…

⚡ ATTACK CHAIN
CVSS vector not available. Review vendor advisory.

🌍 REAL WORLD IMPACT

🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add WAF rule, create IDS alert for anomalous traffic.

⚠️ URGENCY
📌 Low priority — routine update sufficient.

────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]

Target Reconnaissance Queries (FOFA & Shodan)
CVSS Score
0 / 10 · CVSS NONE
Related CVEs
0.0
CVE-2026-108687
The SAML SSO Login WordPress plugin through 1.5.2 does not verify that the SAML assertion whose signature it
0.0
CVE-2026-121852
The AppPresser WordPress plugin before 5.0.0 does not properly escape the contents of its debug log when disp
0.0
CVE-2026-129446
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) WordPress plugin before 45.4 does not
0.0
CVE-2026-120404
The built-in regular expression name finder for latitude and longitude coordinates uses a pattern that is vuln
0.0
CVE-2026-99321
In the Linux kernel, the following vulnerability has been resolved: rust_binder: wake epoll on self-work queu
0.0
CVE-2026-99322
In the Linux kernel, the following vulnerability has been resolved: ksmbd: rebind completed CREATE replays wi