CVE-2024-36953: KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr()
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgicv2parseattr()
The Linux kernel CVE team has assigned CVE-2024-36953 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024053040-CVE-2024-36953-fc12@gregkh/T
Other sources
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgicv2parseattr()
vgicv2parseattr() is responsible for finding the vCPU that matches the user-provided CPUID, which (of course) may not be valid. If the ID is invalid, kvmgetvcpubyid() returns NULL, which isn't handled gracefully.
Similar to the GICv3 uaccess flow, check that kvmgetvcpubyid() actually returns something and fail the ioctl if not.
— NVD
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-36953?
CVE-2024-36953 has been categorized as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2024-36953?
To mitigate CVE-2024-36953, update your Linux kernel to a version that is patched, such as 5.10.217, 5.15.159, or later.
Which versions of the Linux kernel are affected by CVE-2024-36953?
CVE-2024-36953 affects several versions of the Linux kernel prior to the specified remedied versions, including 5.10.217 and 6.1.91.
What systems are vulnerable to CVE-2024-36953?
Systems running vulnerable versions of the Linux kernel, particularly on ARM64 architectures with KVM enabled, are susceptible to CVE-2024-36953.
Is there a specific exploit associated with CVE-2024-36953?
There is currently no publicly available exploit for CVE-2024-36953, but it is important to apply the patch to prevent potential exploitation.