Vulnerability in Kernel: KVM: VMX: Disable preemption when probing user return MSRs
Summary
GSD-2021-1000310: KVM: VMX: Disable preemption when probing user return MSRs. Affects Kernel versions >= 4be5341026246870818e28b53202b001426a5aec, < 31f29749ee970c251b3a7e5b914108425940d089. 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 is a fundamental component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. It is crucial for the proper functioning of the entire system. This vulnerability specifically affects the Kernel's KVM (Kernel-based Virtual Machine) module, which enables virtualization on Linux systems. KVM allows users to run multiple virtual machines on a single physical machine. The vulnerability arises from a flaw in the handling of user return MSRs (Model Specific Registers) during the probing process.
Vulnerability Detail
The vulnerability in the Kernel's KVM module allows an attacker to exploit the probing of user return MSRs, potentially leading to unauthorized access or privilege escalation within a virtual machine. By leveraging this vulnerability, an attacker could execute arbitrary code or gain elevated privileges within the virtualized environment. The vulnerability was introduced in version v5.5 of the Linux Kernel and was fixed in version v5.10.38. It is important to note that the impact and attack plausibility of this vulnerability have not been proven.
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
There is no specific workaround mentioned for this vulnerability.
Conclusion
In conclusion, the vulnerability in the Kernel's KVM module could potentially allow an attacker to gain unauthorized access or escalate privileges within a virtual machine. It is crucial to update the Linux Kernel to version v5.10.38 or later to address 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 potentially allow an attacker to gain unauthorized access or escalate privileges within a virtual machine.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time monitoring and alerts for open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
No, this vulnerability requires an attacker to have access to a virtual machine running on the affected system. It cannot be exploited remotely.
The recommended solution is to update the Linux Kernel to the fixed version. However, if updating is not immediately feasible, implementing strict access controls and monitoring within the virtualized environment can help mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
