Skip to main content
VulnerabilityPublished

CVE-2026-99585: Linux kernel · KVM: arm64: Use kvm_s2_fault_vma_info in gmem_abort()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 09462113ed3906929b228144a738e7b15cb9f52d : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:19 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a7b57e0995927cc5fb8629594e2abf2a6f1000e9, < 09462113ed3906929b228144a738e7b15cb9f52d
Fixed in
  • 09462113ed3906929b228144a738e7b15cb9f52d
LinuxLinuxAffected
  • ≥ a7b57e0995927cc5fb8629594e2abf2a6f1000e9, < 80b0b86dc5e4344e62a2fd3ee43d0ef816fe9122
Fixed in
  • 80b0b86dc5e4344e62a2fd3ee43d0ef816fe9122
LinuxLinuxAffected
  • ≥ a7b57e0995927cc5fb8629594e2abf2a6f1000e9, < 9f84bde6aaade57b2ef7b71c1783b30773cd43d6
Fixed in
  • 9f84bde6aaade57b2ef7b71c1783b30773cd43d6
LinuxLinuxAffected
  • =6.18
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

Community reviews

Loading reviews…