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.
Update Linux/Linux to 918450ad6010df6ecd2efde12a1409e011da22d6 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanKVM: arm64: Reassign nested_mmus array behind mmu_lock affects Linux/Linux (generic), Linux/Linux (generic). Severity is high. 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.
AI coding agents often install or upgrade packages automatically in generic. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
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.
Update Linux/Linux to 918450ad6010df6ecd2efde12a1409e011da22d6 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanKVM: arm64: Reassign nested_mmus array behind mmu_lock affects Linux/Linux (generic), Linux/Linux (generic). Severity is high. 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.
AI coding agents often install or upgrade packages automatically in generic. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric |
|---|
| >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <918450ad6010df6ecd2efde12a1409e011da22d6 || >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <4424dbcb06d68e34e51c019a5781a7dc00731971 || >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <70543358fa08e0f7cebc3447c3b70fe97ad7aaa8 |
| 918450ad6010df6ecd2efde12a1409e011da22d6, 4424dbcb06d68e34e51c019a5781a7dc00731971, 70543358fa08e0f7cebc3447c3b70fe97ad7aaa8 |
| Linux/Linuxgeneric | 6.11 | Not reported |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by CVE List V5 (cvelist).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| Linux/Linuxgeneric |
|---|
| >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <918450ad6010df6ecd2efde12a1409e011da22d6 || >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <4424dbcb06d68e34e51c019a5781a7dc00731971 || >=4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <70543358fa08e0f7cebc3447c3b70fe97ad7aaa8 |
| 918450ad6010df6ecd2efde12a1409e011da22d6, 4424dbcb06d68e34e51c019a5781a7dc00731971, 70543358fa08e0f7cebc3447c3b70fe97ad7aaa8 |
| Linux/Linuxgeneric | 6.11 | Not reported |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by CVE List V5 (cvelist).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard