Vulnerability in drm/msm/disp/dpu1 Package: Avoid Clearing HW Interrupts if hw_intr is Null during DRM Uninit
Summary
GSD-2022-1002769: drm/msm/disp/dpu1: avoid clearing hw interrupts if hw_intr is null during drm uninit. Affects Kernel versions >= f25f656608e3a54ac3e0747be415cf3d4a69cef8, < a800701429313149afde18d98821554fbfcb3164. 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 is responsible for managing display and graphics functionality on devices that utilize the Qualcomm Adreno GPU. The package includes drivers and modules that enable communication between the GPU and the display hardware. 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 occurs due to a missing null check in the code of the drm/msm/disp/dpu1 package. During the DRM uninit process, if the hw_intr variable is null, the package attempts to clear hardware interrupts, leading to potential memory corruption or other undefined behavior. An attacker could potentially exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial of service. 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
In conclusion, the vulnerability in the drm/msm/disp/dpu1 package allows for potential memory corruption or other undefined behavior due to a missing null check during DRM uninit. It is crucial to update the Linux Kernel to version v5.18.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially allow an attacker to execute arbitrary code, escalate privileges, or cause a denial of service.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.
There is currently no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
The recommended mitigation is to update the Linux Kernel to version v5.18.3 or later, which includes the fix for this vulnerability.
You can find more information about this vulnerability in the GSD-2022-1002769 entry of the GSD Database maintained by the Cloud Security Alliance. The source link is provided in the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
