Linux kernel guest memory mapping failure in arm64 pKVM
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.647.3.57.4-rc1In 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.
From the CVE record · Linux
KVM arm64 can repeatedly fault when a guest_memfd-backed guest faults past the first 4K of a page on a pKVM host with pages larger than 4K. The guest can trigger the fault; the input does not specify authentication requirements or user interaction. Nested guest faults can also report a noncanonical address in the memory fault exit.
Operators of Linux kernel pKVM hosts running guest_memfd-backed guests, especially with page sizes larger than 4K, should check their kernel versions against the vendor advisory; affected versions are not specified.