KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN
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.407.1.57.2In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN
kvm_handle_vncr_abort() assumes that s1_walk_result conveys an abort when kvm_translate_vncr() returns -EFAULT. This is not always the case as it's possible to encounter 'late' failures on the output of S1 translation, e.g. a GFN outside of the memslots.
Fix it by preparing an external abort before returning from kvm_translate_vncr(). Get rid of the BUG_ON() in the fault injection path while at it.
From the CVE record · Linux
Linux KVM on arm64 can mishandle a nested-virtualization abort when translation succeeds initially but later cannot resolve a page frame, such as when a GFN is outside the memslots. The fault-injection path contains a BUG_ON() under these conditions. The input does not specify how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running Linux with KVM arm64 nested virtualization should check their kernel; affected versions are not specified.