CVE-2026-99472
KVM: pfncache: use a dedicated invalidation sequence for cache refresh
No exploitation reported by the sources we read.
- Published2026-11-19
- Fixed in7.3.2
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: pfncache: use a dedicated invalidation sequence for cache refresh The gfn_to_pfn_cache refresh path guards against mmu notifier invalidations which complete while it has dropped gpc->lock for the HVA->PFN lookup: hva_to_pfn_retry() samples kvm->mmu_invalidate_seq and retries if it changed, or if mn_active_invalidate_count is still elevated. That is insufficient for HVA-based caches. mmu_invalidate_seq is only advanced by kvm_mmu_invalidate_end() when the invalidated range overlaps a memslot, and an HVA-based cache (e.g. the Xen shared_info page mapped with KVM_XEN_ATTR_TYPE_SHARED_INFO_HVA) need not be backed by any memslot at all. An invalidation of the cached HVA which starts and ends entirely within the lookup window is thus invisible to the retry check: mn_active_invalidate_count is back to zero and the sequence never moved. The refresh then publishes a mapping of a page which has already been freed, and the next reader dereferences it: BUG: KASAN: use-after-free in kvm_xen_shared_info_init+0x3c6/0x440 Read of size 4 at addr ffff8880599c2900 by task syz.2.383/7257 Since gfn_to_pfn_cache_invalidate_start() deliberately skips caches which are not currently valid (including one whose refresh is in progress, as the refresh clears the valid flag before dropping the lock), the retry check is the only line of defence, and it must fire for *any* invalidation, not just those hitting a memslot. Add a dedicated kvm->gpc_invalidate_seq, incremented by every kvm_mmu_notifier_invalidate_range_end() under mn_invalidate_lock before mn_active_invalidate_count is decremented, and check it in hva_to_pfn_retry() instead of mmu_invalidate_seq. Incrementing in range_end() in the same critical section as the in-progress count also closes the variant where the cache is activated with the contested HVA only after invalidate_range_start() has run. The same bug is also reachable through the per-vCPU vcpu_info cache (KVM_XEN_VCPU_ATTR_TYPE_VCPU_INFO_HVA), where the stale mapping is then dereferenced by kvm_setup_guest_pvclock() on the next KVM_RUN: BUG: KASAN: use-after-free in kvm_setup_guest_pvclock+0x5bf/0x660 This intentionally makes refresh retry on *unrelated* mmu notifier events; restoring precision (and reworking the GPC locking more generally) is left for a subsequent series. Reproducers: https://david.woodhou.se/xen_shinfo_race.c https://david.woodhou.se/vcpu_info_race.c
Timeline
dates in UTC- 2026-11-1914:42CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 6.9.0, < 7.3.2 | 7.3.2 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ b9220d32799a62c634f7b0b3618da52772626952, < fabc002f6396202b5ad7ad4ceec24d27aad90f3ffixed in fabc002f6396202b5ad7ad4ceec24d27aad90f3fgit
- ≥ b9220d32799a62c634f7b0b3618da52772626952, < da260bcb56feeb6489a83f310308453a0a7de25efixed in da260bcb56feeb6489a83f310308453a0a7de25egit
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 6.9no fix stated
Not affected < 6.9 · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-19
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- linuxDebian:14all versions · fixed in 7.3.3-1
- linuxDebian:13all versions · no fixed version listed
- linux-ltsAlpaquita:streamfrom 6.18.64-r0 · no fixed version listed
- linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
Vendor advisories
- CVE-2026-99472 Red Hat Product Security
kernel: kernel: KVM: denial of service via use-after-free in pfncache
Fix
- Update Linux kernel to 7.3.2
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-20
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-22
- CNACVSS 3.17.82026-11-22
- FIRST EPSSEPSS score0.2 %2026-11-21
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-130144same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-6cjq-7h3x-f93msame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-11-19
- Last modified
- 2026-11-22
- NVD status
- Received
- GitHub advisory
- GHSA-6cjq-7h3x-f93m
Frequently asked questions
What is CVE-2026-99472?
Is CVE-2026-99472 actively exploited?
What is the CVSS score for CVE-2026-99472?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website checks · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-6cjq-7h3x-f93m
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0