KVM: arm64: nv: Fix life cycle of the nested_mmus array
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 33346f8960c7bb6a3b4e273b5cfe25c5a8be349f, Kernel 512c93f4461b9a3735987f48423d438a9cd49e6a, Kernel 81e3f065a6485626f816d791dfd5e00ddd12eff5 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Fix life cycle of the nested_mmus array The nested_mmus array holds the shadow page tables that are used when a guest is running a nested context. These structures are allocated on VCPU_INIT for whole guest, which implies that they may have to be relocated as the array grows. Should a VCPU_INIT occur whilst a vcpu is actively running an L2 and that the allocation requires relocation, that vcpu will still be running with a pointer to the previous structure, which will have been freed. Fix this by turning the array of structures to an array of pointers, which is now allocated at VM creation, sized to the absolute maximum that KVM can handle. In turn, each VCPU_INIT contributes S2_MMU_PER_VCPU to the pool. No reallocation is ever performed, and the life cycle of each object is much clearer: - the nested_mmus array is allocated in kvm_init_nested(), and freed in kvm_arch_destroy_vm() - s2_mmu structures are allocated in kvm_vcpu_init_nested(), and freed on kvm_arch_flush_shadow_all() Finally, the freeing of vcpu->arch.vncr_array is made consistent rather than being done on some failure paths, but not others.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.11, >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <33346f8960c7bb6a3b4e273b5cfe25c5a8be349f, >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <512c93f4461b9a3735987f48423d438a9cd49e6a, >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <81e3f065a6485626f816d791dfd5e00ddd12eff5, >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <ea242bdc29e8a8ff0e2447a64b3841114779f3af | 33346f8960c7bb6a3b4e273b5cfe25c5a8be349f, 512c93f4461b9a3735987f48423d438a9cd49e6a, 81e3f065a6485626f816d791dfd5e00ddd12eff5, ea242bdc29e8a8ff0e2447a64b3841114779f3af |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket