KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory
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 guest VNCR isn't normal memory
When constructing an L1 VNCR mapping, KVM unconditionally uses cacheable memory attributes, even if the underlying PFN isn't memory. This gets particularly hairy if the endpoint doesn't support cacheable memory attributes, potentially throwing an SError on writeback...
While KVM does permit cacheable memory attributes on certain PFNMAP VMAs, kvm_translate_vncr() isn't currently grabbing the VMA. So do the simpler thing for now and just reject everything that isn't memory.
From the CVE record · Linux
KVM on arm64 can assign cacheable memory attributes to an L1 guest VNCR mapping even when the underlying PFN is not memory. If the endpoint does not support those attributes, writeback may trigger an SError. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with KVM on arm64 should check their installations; affected versions are not specified.