Null Pointer Dereference in drm/msm Package
Summary
GSD-2021-1001935: drm/msm: Fix null pointer dereference on pointer edp. Affects Kernel versions >= ab5b0107ccf3821a6837b0f2819270d6fa0b278f, < bacac7d26849c8e903ceb7466d9ce8dc3c2797eb. 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 that provides support for graphics rendering on Qualcomm Adreno GPUs. It is responsible for managing display resources and handling communication between the GPU and the display hardware. The package is widely used in various Linux-based operating systems and is critical for proper graphics functionality on devices with Qualcomm GPUs.
Vulnerability Detail
The vulnerability identified in the drm/msm package is a null pointer dereference on the 'edp' pointer. This vulnerability can be exploited by an attacker to cause a denial-of-service (DoS) condition or potentially execute arbitrary code. The null pointer dereference occurs when the 'edp' pointer is accessed without proper validation, leading to a crash or system instability. 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 provided for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel.
Conclusion
The null pointer dereference vulnerability in the drm/msm package can lead to a denial-of-service condition or potential execution of arbitrary code. It is crucial to update the Linux Kernel to version v4.9.288 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from a denial-of-service (DoS) condition to potential execution of arbitrary code. However, the actual impact and attack plausibility have not been proven yet.
You can use the Vulert Playground at Vulert 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 monitoring and alerts for open-source vulnerabilities, including this one.
Yes, a patch for this vulnerability is available in the Linux Kernel version v4.9.288. It is recommended to update the Kernel to this version or later to apply the fix.
There are no known exploits for this vulnerability at the moment. However, it is still important to apply the fix to prevent any potential exploitation in the future.
This vulnerability was discovered by an automated ID intended to aid in the discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
