NULL pointer dereference in convert_variable_location() in Kernel
Summary
GSD-2021-1000795: perf probe: Fix NULL pointer dereference in convert_variable_location(). Affects Kernel versions >= 66f69b2197167cb99330c77a550da50f1f597abc, < eba7c76a5651392a9132c54aceddc5af8cfb0938. 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 critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It is responsible for managing system resources, including memory, processes, and input/output operations. The vulnerability in question affects the Kernel's perf probe feature, which allows users to dynamically instrument kernel functions for performance analysis. The convert_variable_location() function within perf probe is susceptible to a NULL pointer dereference, which can lead to a system crash or potential code execution.
Vulnerability Detail
The vulnerability arises from a NULL pointer dereference in the convert_variable_location() function of perf probe. When processing certain variable locations, the function fails to check for a NULL pointer, leading to a crash or potential code execution. An attacker could potentially exploit this vulnerability to crash the system or execute arbitrary code with kernel privileges. 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 NULL pointer dereference vulnerability in the convert_variable_location() function of perf probe in the Kernel can lead to system crashes or potential code execution. It is crucial to update the Kernel to version v5.12.10 or later to mitigate this vulnerability. Regularly updating the Kernel is recommended to ensure the latest security patches are applied. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a system crash or potential code execution, potentially allowing an attacker to gain kernel-level privileges.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will provide real-time alerts for open-source vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the necessary updates to mitigate the risk.
The vulnerability requires local access to the system, as it involves kernel-level operations. However, if an attacker gains local access, they can potentially exploit this vulnerability.
The primary mitigation is to update the Kernel to version v5.12.10 or later, which includes the fix for this vulnerability. Regularly updating the Kernel is recommended to stay protected against potential security vulnerabilities.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
