KVM: arm64: Tear down vGIC on failed vCPU creation
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.8epss 0.3%
exploitation probability
0.3%top 84% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/07476e0d932afc53c05468076393ac35d0b4999ehttps://git.kernel.org/stable/c/2480326eba8ae9ccc5e4c3c2dc8d407db68e3c52https://git.kernel.org/stable/c/250f25367b58d8c65a1b060a2dda037eea09a672https://git.kernel.org/stable/c/5085e02362b9948f82fceca979b8f8e12acb1cc5https://git.kernel.org/stable/c/c322789613407647a05ff5c451a7bf545fb34e73https://git.kernel.org/stable/c/f1e9087abaeedec9bf2894a282ee4f0d8383f299https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html