Vulnerability in Kernel package: KVM: SVM: Use online_vcpus, not created_vcpus, to iterate over vCPUs
Summary
GSD-2021-1000298: KVM: SVM: Use online_vcpus, not created_vcpus, to iterate over vCPUs. Affects Kernel versions >= ad73109ae7ec30d5bfb76be108e304f9f0af4829, < ba7bf5d6336aa9c0d977b161bfa420c56d46ee40. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Kernel package is a critical component of the Linux operating system that provides core functionality and acts as an interface between the hardware and software layers. It includes various subsystems, such as memory management, process scheduling, and device drivers. The Kernel package is responsible for managing the system's resources and ensuring the proper execution of user applications. This vulnerability specifically affects the Kernel's KVM (Kernel-based Virtual Machine) subsystem, which enables running virtual machines on the host system using hardware virtualization extensions.
Vulnerability Detail
The vulnerability identified in the KVM subsystem of the Kernel package involves the incorrect usage of vCPU iteration. The code uses the 'created_vcpus' variable instead of 'online_vcpus' to iterate over the virtual CPUs (vCPUs) of a guest virtual machine. This can lead to various issues, including incorrect handling of vCPUs, potential crashes, and security vulnerabilities. An attacker with access to a guest virtual machine could potentially exploit this vulnerability to gain elevated privileges or execute arbitrary code on the host system. It is important to note that the impact and attack plausibility of this vulnerability have not been proven yet.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a workaround, users can apply patches or backport the fix to their current Kernel version. Alternatively, if updating the Kernel is not feasible, users can consider disabling the KVM subsystem or restricting access to guest virtual machines to mitigate the potential risks associated with this vulnerability.
Conclusion
The vulnerability in the Kernel package's KVM subsystem can lead to various issues, including incorrect handling of vCPUs, potential crashes, and security vulnerabilities. It is crucial to update the Kernel to version v5.12.4 or later to fix this vulnerability. Users can also apply patches or backport the fix to their current Kernel version as a workaround. Disabling the KVM subsystem or restricting access to guest virtual machines can also help mitigate the risks associated with this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from incorrect handling of vCPUs and potential crashes to potential security vulnerabilities. An attacker with access to a guest virtual machine could potentially exploit this vulnerability to gain elevated privileges or execute arbitrary code on the host system.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in software.
Yes, a fix for this vulnerability is available in Linux Kernel version v5.12.4 and later. It is recommended to update the Kernel package to the latest version to mitigate the vulnerability.
Yes, users can apply patches or backport the fix to their current Kernel version. Alternatively, if updating the Kernel is not feasible, users can consider disabling the KVM subsystem or restricting access to guest virtual machines to mitigate the potential risks associated with this vulnerability.
You can find more information about this vulnerability in the vulnerability database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2021-1000298, and the details can be accessed at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000298.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
