KVM: arm64: Fix circular locking dependency
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.186.7.66.8In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Fix circular locking dependency
The rule inside kvm enforces that the vcpu->mutex is taken *inside* kvm->lock. The rule is violated by the pkvm_create_hyp_vm() which acquires the kvm->lock while already holding the vcpu->mutex lock from kvm_vcpu_ioctl(). Avoid the circular locking dependency altogether by protecting the hyp vm handle with the config_lock, much like we already do for other forms of VM-scoped data.
From the CVE record · Linux
Linux KVM on arm64 has a circular locking dependency when VM creation takes kvm->lock while a vCPU ioctl already holds vcpu->mutex. This could cause a deadlock during local ioctl use; the input does not specify authentication requirements or any additional user interaction.
Engineers running Linux kernels with KVM on arm64 should check their kernel versions against the vendor advisory; affected versions are not specified.