KVM: x86: Forcibly leave nested virt when SMM state is toggled
Summary
GSD-2022-1000188: KVM: x86: Forcibly leave nested virt when SMM state is toggled. Affects Kernel versions < 080dbe7e9b86a0392d8dffc00d9971792afc121f. 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 crucial component of the Linux operating system. It provides the core functionality and acts as an interface between the hardware and software layers. KVM (Kernel-based Virtual Machine) is a module within the Kernel that enables virtualization on x86 architectures. It allows multiple virtual machines to run concurrently on a single physical machine. This vulnerability specifically affects the x86 architecture when nested virtualization is enabled and the System Management Mode (SMM) state is toggled.
Vulnerability Detail
The vulnerability arises when the SMM state is toggled while nested virtualization is active. SMM is a special operating mode in x86 processors that provides firmware-based system management functions. By exploiting this vulnerability, an attacker with access to a virtual machine can escape the virtualization layer and gain unauthorized access to the host system or other virtual machines. 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
There is no specific workaround mentioned for this vulnerability.
Conclusion
The KVM vulnerability in the x86 architecture, related to toggling the SMM state during nested virtualization, has been identified. While the impact and attack plausibility have not been proven, it is crucial to update the Linux Kernel to version v5.10.97 or later to mitigate any potential risks. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but if successfully exploited, an attacker could escape the virtualization layer and gain unauthorized access to the host system or other virtual machines.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. It does not require any signup and can monitor and alert in real-time for open-source vulnerabilities.
Yes, the vulnerability has been fixed in the Linux Kernel version v5.10.97. Users should update their Kernel to this version or a later one.
The details regarding remote exploitation have not been provided. It is recommended to apply the fix as soon as possible to mitigate any potential risks.
There are no known instances of this vulnerability being exploited at the moment.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
