KVM: arm64: Tear down vGIC on failed vCPU creation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6211753fdfd05af9e08f54c8d0ba3ee516034878 · < 250f25367b58d8c65a1b060a2dda037eea09a672| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Tear down vGIC on failed vCPU creation
If kvm_arch_vcpu_create() fails to share the vCPU page with the hypervisor, we propagate the error back to the ioctl but leave the vGIC vCPU data initialised. Note only does this leak the corresponding memory when the vCPU is destroyed but it can also lead to use-after-free if the redistributor device handling tries to walk into the vCPU.
Add the missing cleanup to kvm_arch_vcpu_create(), ensuring that the vGIC vCPU structures are destroyed on error.
From the CVE record · Linux
In the Linux kernel's KVM arm64 code, a failure to share a vCPU page with the hypervisor can leave vGIC vCPU data initialized after vCPU creation fails. Subsequent redistributor device handling may access freed memory; the input does not specify attacker access requirements or user interaction.
Teams running Linux kernels with KVM on arm64 should check their exposure; affected versions are not specified.