KVM: arm64: Reassign nested_mmus array behind mmu_lock
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4424dbcb06d68e34e51c019a5781a7dc00731971, Kernel 70543358fa08e0f7cebc3447c3b70fe97ad7aaa8 and Kernel 918450ad6010df6ecd2efde12a1409e011da22d6.
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Reassign nested_mmus array behind mmu_lock kvm->arch.nested_mmus[] is walked under kvm->mmu_lock, including from the MMU notifier path (kvm_unmap_gfn_range() -> kvm_nested_s2_unmap()), which can run at any time. kvm_vcpu_init_nested() reallocates the array and frees the old buffer while holding only kvm->arch.config_lock, so such a walker can reference the freed array. Allocate the new array outside of mmu_lock, as the allocation can sleep. Under the lock, copy the existing entries, fix up the back pointers and reassign the array. Free the old buffer after dropping the lock, as kvfree() can sleep as well.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.11, >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <4424dbcb06d68e34e51c019a5781a7dc00731971, >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <70543358fa08e0f7cebc3447c3b70fe97ad7aaa8, >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <918450ad6010df6ecd2efde12a1409e011da22d6 | 4424dbcb06d68e34e51c019a5781a7dc00731971, 70543358fa08e0f7cebc3447c3b70fe97ad7aaa8, 918450ad6010df6ecd2efde12a1409e011da22d6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket