Null Pointer Dereference in drm/msm Package
Summary
UVI-2021-1002002: drm/msm: Fix null pointer dereference on pointer edp. Affects Kernel versions >= ab5b0107ccf3821a6837b0f2819270d6fa0b278f, < f302be08e3de94db8863a0b2958b2bb3e8e998e6. 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 drm/msm package is a component of the Linux Kernel, specifically designed for supporting graphics and display functionality on Qualcomm Adreno GPUs. It provides the necessary drivers and interfaces for managing display controllers, connectors, and panels. The package plays a critical role in enabling graphics rendering and output on devices utilizing Qualcomm GPUs.
Vulnerability Detail
The vulnerability identified as UVI-2021-1002002 is a null pointer dereference issue within the drm/msm package. This vulnerability occurs when a null pointer is accessed, leading to a system crash or potential privilege escalation. The vulnerability was introduced in version v4.0 of the Linux Kernel and affects all subsequent versions until v5.4.155. 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
No specific workaround has been provided for this vulnerability. It is advised to apply the fix by updating the Linux Kernel to the recommended version.
Conclusion
The null pointer dereference vulnerability in the drm/msm package of the Linux Kernel can lead to system crashes or potential privilege escalation. It is crucial to update the Kernel to version v5.4.155 or later to address this vulnerability. No known exploits exist at the moment, but prompt remediation is advised. For additional support, 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 the attacker's capabilities.
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 to the playground, and it will provide real-time alerts for any open-source vulnerabilities, including this one.
As of now, there are no known exploits for this vulnerability. However, it is crucial to apply the fix promptly to mitigate any potential risks.
The remote exploitability of this vulnerability has not been determined yet. However, it is always recommended to keep systems up to date to minimize the risk of remote attacks.
For further support and assistance in vulnerability remediation, you can reach out to info@devnack.com. The Devnack team will provide guidance and help ensure your system is secure.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
