CVE-2026-99585: Linux kernel · KVM: arm64: Use kvm_s2_fault_vma_info in gmem_abort()
Source GCVE Database
Not known to be exploited · fixed in 09462113ed3906929b228144a738e7b15cb9f52d : update Linux kernel when convenient.
Data as of 20 Nov 2026, 07:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 09462113ed3906929b228144a738e7b15cb9f52d, 80b0b86dc5e4344e62a2fd3ee43d0ef816fe9122, 9f84bde6aaade57b2ef7b71c1783b30773cd43d6
Exploitation evidence
Disclosed: evidence found.
CVE published 20 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 19 Nov 2026.
What to do
Upgrade Linux kernel to 09462113ed3906929b228144a738e7b15cb9f52d, 80b0b86dc5e4344e62a2fd3ee43d0ef816fe9122 or 9f84bde6aaade57b2ef7b71c1783b30773cd43d6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Use kvm_s2_fault_vma_info in gmem_abort() gmem_abort() maps at s2fd->fault_ipa, which HPFAR_EL2 holds at 4K granularity whatever the page size. The generic page-table code aligns it, but pkvm_pgtable_stage2_map() looks up existing mappings over [addr, addr + size), so on a pKVM host with pages larger than 4K a guest_memfd-backed guest that faults past the first 4K of a page can find its neighbour's mapping, get -EAGAIN and take the same fault forever. The memory fault exit reports s2fd->fault_ipa too, which for a nested guest's fault is the nested IPA rather than the canonical one kvm_gmem_get_pfn() failed on. Take the addresses from kvm_s2_fault_vma_info instead, as user_mem_abort() does, and report the canonical gfn in the memory fault exit. kvm_s2_fault_get_vma_info() itself isn't called: a guest_memfd memslot's userspace_addr doesn't need to be backed by a VMA.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99585 (opens in a new tab)
- git.kernel.org/stable/c/09462113ed3906929b228144a738e7b15cb9f52d (opens in a new tab)
- git.kernel.org/stable/c/80b0b86dc5e4344e62a2fd3ee43d0ef816fe9122 (opens in a new tab)
- git.kernel.org/stable/c/9f84bde6aaade57b2ef7b71c1783b30773cd43d6 (opens in a new tab)