Linux
KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2a359e072596fcb2e9e85017a865e3618a2fe5b5, < d5436e18e4fc2886ac306304d884ea3b92e1edbf
- >= 2a359e072596fcb2e9e85017a865e3618a2fe5b5, < bc00e0e376ee3572f5d26c174473abef1e35decc
- >= 2a359e072596fcb2e9e85017a865e3618a2fe5b5, < 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6
Fixed in d5436e18e4fc2886ac306304d884ea3b92e1edbf, bc00e0e376ee3572f5d26c174473abef1e35decc, 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6
- 6.16
Fixed in 0, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to d5436e18e4fc2886ac306304d884ea3b92e1edbf or bc00e0e376ee3572f5d26c174473abef1e35decc or 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6 or later.
Upgrade Linux to 0 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.