Vulnerability in Kernel: x86/sev-es: Don't return NULL from sev_es_get_ghcb()
Summary
GSD-2021-1000492: x86/sev-es: Don't return NULL from sev_es_get_ghcb(). Affects Kernel versions >= 0786138c78e79343c7b015d77507cbf9d5f15d00, < efbfc33b0b1c241311553d3c2229974ec1d684e2. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware. It manages system resources, facilitates communication between software and hardware, and ensures the security and stability of the system. This vulnerability specifically affects the x86/sev-es subsystem of the Kernel. The x86/sev-es subsystem is responsible for handling Secure Encrypted Virtualization (SEV) for AMD processors. SEV allows for the encryption of virtual machines, enhancing their security. However, a flaw in the implementation of sev_es_get_ghcb() function can lead to a NULL pointer dereference, potentially resulting in a system crash or privilege escalation.
Vulnerability Detail
The vulnerability arises from the sev_es_get_ghcb() function in the x86/sev-es subsystem of the Kernel. This function is responsible for retrieving the Guest Hypervisor Communication Block (GHCB) associated with a Secure Encrypted Virtualization (SEV) guest. However, due to a coding error, the function may return a NULL pointer in certain scenarios. This NULL pointer can subsequently cause a system crash or be exploited by an attacker to gain elevated privileges. The impact and attack plausibility of this vulnerability have not been fully proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v5.12.7 by commit efbfc33b0b1c241311553d3c2229974ec1d684e2. The vulnerability was introduced in version v5.10 by commit 0786138c78e79343c7b015d77507cbf9d5f15d00.
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 vulnerability in the x86/sev-es subsystem of the Kernel, specifically in the sev_es_get_ghcb() function, can lead to a NULL pointer dereference and potential system crashes or privilege escalation. It is crucial to update the Linux Kernel to version v5.12.7 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from a system crash to potential privilege escalation, depending on how it is exploited.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and it will analyze the dependencies for any known vulnerabilities.
Yes, a patch has been released in Linux Kernel version v5.12.7. It is recommended to update to this version or a later one to mitigate the vulnerability.
The exact attack vector and exploitability of this vulnerability have not been fully proven yet. However, it is always recommended to keep systems up to date with the latest security patches to minimize the risk of remote exploitation.
There are no known instances of this vulnerability being exploited in the wild at the time of this report. However, it is important to apply the necessary updates to protect against potential future exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
