First published: Fri May 09 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2025-37849 is rated as medium due to its impact on the virtual GIC in the Linux kernel.
To fix CVE-2025-37849, ensure that you apply the latest patches for the Linux kernel provided by your distribution.
CVE-2025-37849 affects various versions of the Linux kernel that utilize KVM on arm64 systems.
The impact of CVE-2025-37849 can lead to unintended behavior during vCPU creation due to initialized vGIC data.
CVE-2025-37849 is not directly exploitable remotely as it involves local interactions with the hypervisor.