Vulnerability in drm/msm/disp/dpu1 Package: Avoid Clearing HW Interrupts if hw_intr is Null during DRM Uninit
Summary
GSD-2022-1003127: drm/msm/disp/dpu1: avoid clearing hw interrupts if hw_intr is null during drm uninit. Affects Kernel versions >= f25f656608e3a54ac3e0747be415cf3d4a69cef8, < a7ca30c3a8b2e8bda65f2b922d382ac056be8aa4. 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/disp/dpu1 package is a component of the Linux Kernel ecosystem. It provides support for display and graphics rendering on Qualcomm Adreno GPUs. The package includes drivers and firmware for managing the display pipeline and hardware interrupts. The vulnerability in question arises when the package attempts to clear hardware interrupts without checking if the hw_intr variable is null during the DRM (Direct Rendering Manager) uninitialization process.
Vulnerability Detail
The vulnerability allows an attacker to trigger a null pointer dereference, leading to a kernel crash or potential privilege escalation. By exploiting this vulnerability, an attacker could potentially execute arbitrary code with kernel-level privileges. The issue was introduced in version v5.16 of the Linux Kernel and was fixed in version v5.17.14. The vulnerability was discovered and reported by an automated security analysis tool, and its impact and attack plausibility have not been proven.
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 drm/msm/disp/dpu1 package of the Linux Kernel allows for a null pointer dereference during DRM uninitialization. This can result in a kernel crash or potential privilege escalation. It is crucial to update the Linux Kernel to version v5.17.14 or later, which includes the necessary fix. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a kernel crash or potential privilege escalation, allowing an attacker to execute arbitrary code with kernel-level privileges.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It analyzes your manifest file (e.g., package-lock.json) and provides real-time alerts for open-source vulnerabilities.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
The exact attack vector and exploitability of this vulnerability have not been proven. However, it is always recommended to keep systems up to date with the latest security patches to minimize the risk of remote exploitation.
This vulnerability was discovered and reported by an automated security analysis tool. The tool identified the issue during its analysis of the Linux Kernel source code.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
