CVE-2026-99472: Linux kernel · KVM: pfncache: use a dedicated invalidation sequence for cache refresh
Source GCVE Database
Not known to be exploited : upgrade to fabc002f6396202b5ad7ad4ceec24d27aad90f3f or da260bcb56feeb6489a83f310308453a0a7de25e soon.
Data as of 19 Nov 2026, 17:19 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in fabc002f6396202b5ad7ad4ceec24d27aad90f3f, da260bcb56feeb6489a83f310308453a0a7de25e
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 fabc002f6396202b5ad7ad4ceec24d27aad90f3f or da260bcb56feeb6489a83f310308453a0a7de25e.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by introducing a dedicated invalidation sequence for cache refresh. Users should apply the official kernel updates that include this patch once available. Until patched, affected systems remain vulnerable. No vendor advisory content was provided to indicate alternative mitigations or workarounds.
Description
A use-after-free vulnerability exists in the Linux kernel's KVM pfncache refresh mechanism. The flaw arises because the existing invalidation sequence does not cover all cases of cache invalidation, particularly for HVA-based caches not backed by memslots. This can lead to stale mappings being published and dereferenced, causing kernel memory corruption. The issue affects the Xen shared_info page and per-vCPU vcpu_info cache, potentially leading to kernel crashes detected by KASAN.