KVM: arm64: nv: Inject SEA if guest VNCR isn't normal memory
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6, Kernel bc00e0e376ee3572f5d26c174473abef1e35decc and Kernel d5436e18e4fc2886ac306304d884ea3b92e1edbf.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6, >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <bc00e0e376ee3572f5d26c174473abef1e35decc, >=2a359e072596fcb2e9e85017a865e3618a2fe5b5 <d5436e18e4fc2886ac306304d884ea3b92e1edbf | 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6, bc00e0e376ee3572f5d26c174473abef1e35decc, d5436e18e4fc2886ac306304d884ea3b92e1edbf |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket