Null Pointer Dereference in drm/msm Package
Summary
GSD-2021-1001899: drm/msm: Fix null pointer dereference on pointer edp. Affects Kernel versions >= ab5b0107ccf3821a6837b0f2819270d6fa0b278f, < 46c8ddede0273d1d132beefa9de8b820326982be. 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 and display drivers on Qualcomm Snapdragon SoCs. It is responsible for managing the display subsystem and enabling features such as hardware acceleration and video playback. The package is widely used in various devices running on Linux-based operating systems. However, a vulnerability has been discovered in the package that can lead to a null pointer dereference on the 'edp' pointer.
Vulnerability Detail
The vulnerability in the drm/msm package arises from a null pointer dereference on the 'edp' pointer. This can occur when certain conditions are met, potentially leading to a system crash or privilege escalation. An attacker may be able to exploit this vulnerability to execute arbitrary code or cause a denial of service. The vulnerability was introduced in version v4.0 of the Linux Kernel and has been fixed in version v5.14.14.
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 known workaround for this vulnerability. It is essential to apply the fix by updating the Linux Kernel to a version that includes the necessary patch.
Conclusion
The null pointer dereference vulnerability in the drm/msm package can have severe consequences, including system crashes and privilege escalation. It is crucial to update the Linux Kernel to version v5.14.14 or later to mitigate this vulnerability. For further support and assistance with vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to a system crash or privilege escalation. An attacker may be able to exploit this vulnerability to execute arbitrary code or cause a denial of service.
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 monitoring and alerts for open-source vulnerabilities.
No, there is no known workaround for this vulnerability. It is crucial to update the Linux Kernel to a version that includes the fix.
The fix for this vulnerability is available in version v5.14.14 of the Linux Kernel. You can obtain the latest kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/).
Yes, you can wait for your Linux distribution to release an updated kernel package that includes the fix. Keep an eye on the official channels and update your system as soon as the fix becomes available.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
