KVM: x86/mm: Zap all roots when unmapping gfn range in TDP MMU
Summary
GSD-2022-1001458: KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU. Affects Kernel versions >= b7cccd397f310739fb85383033e95580f99927e0, < 0c8a8da182d4333d9bbb9131d765145568c847b2. 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 an essential component of the Linux operating system. It provides the core functionality and acts as an interface between the hardware and software layers. The KVM (Kernel-based Virtual Machine) subsystem within the Kernel package allows running virtual machines on a host machine. The TDP MMU (Transparent Huge Pages Memory Management Unit) is a component of the KVM subsystem responsible for managing memory mappings for guest virtual machines. This vulnerability affects the TDP MMU in the KVM subsystem.
Vulnerability Detail
The vulnerability in the TDP MMU of the KVM subsystem arises from a failure to properly clear all roots when unmapping a guest frame number (gfn) range. This can lead to the retention of stale pointers, which may be exploited by an attacker to gain unauthorized access or execute arbitrary code within the host machine. 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 TDP MMU vulnerability in the Linux Kernel has been identified and fixed in version v5.16.19. It is recommended to update the Kernel to the latest version to ensure the security of the system. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it has the potential to allow unauthorized access or execution of arbitrary code within the host machine.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
There is no known exploit for this vulnerability at the moment.
The recommended mitigation is to update the Linux Kernel to version v5.16.19 or later, which includes the fix for this vulnerability.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry with ID GSD-2022-1001458.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
