Description
In 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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
2a359e072596fcb2e9e85017a865e3618a2fe5b5 to < d5436e18e4fc2886ac306304d884ea3b92e1edbfaffected2a359e072596fcb2e9e85017a865e3618a2fe5b5 to < bc00e0e376ee3572f5d26c174473abef1e35deccaffected2a359e072596fcb2e9e85017a865e3618a2fe5b5 to < 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6affected
Linux Linux
Default version status: affected
6.16affected0 to < 6.16unaffected6.18.40 to ≤ 6.18.*unaffected7.1.5 to ≤ 7.1.*unaffected7.2 to ≤ *unaffected