Vulnerability in drm/msm/mdp5 Package: Return Error Code in mdp5_pipe_release when Deadlock is Detected
Summary
GSD-2022-1003794: drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected. Affects Kernel versions >= 7907a0d77cb461f58045763c205a5830be72e97c, < b2aa2c4efe93e2580d6a8774b04fe2b99756a322. 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/mdp5 package is a component of the Linux Kernel that provides support for display and graphics functionality on devices using Qualcomm Adreno GPUs. It includes the MDP5 (Multimedia Display Processor 5) driver, which is responsible for managing the display pipelines and hardware resources. The vulnerability in this package relates to the mdp5_pipe_release function, which is used to release a display pipeline when it is no longer needed.
Vulnerability Detail
The vulnerability occurs when a deadlock is detected during the release of a display pipeline in the mdp5_pipe_release function. However, instead of returning an error code to indicate the deadlock, the function does not provide any feedback, potentially leading to incorrect assumptions about the success of the release operation. This could result in resource leaks or other issues if subsequent operations rely on the pipeline being properly released. The vulnerability was introduced in version v4.18 of the Linux Kernel and has been fixed in version v5.4.198.
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 necessary to apply the fix by updating the Linux Kernel.
Conclusion
In conclusion, the vulnerability in the drm/msm/mdp5 package of the Linux Kernel allows for the possibility of resource leaks or other issues if display pipelines are not properly released due to a deadlock. It is crucial to update the Linux Kernel to version v5.4.198 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource leaks or other issues if subsequent operations rely on the proper release of display pipelines.
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 and Vulert will analyze it for any open-source vulnerabilities, including this one.
There is no known exploit for this vulnerability at the time of this report. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
While it is technically possible to manually patch the affected code, it is recommended to update the Linux Kernel to the latest version instead. Manually patching the code can be complex and error-prone, especially for users without extensive knowledge of the Linux Kernel internals.
You can find more information about this vulnerability in the official Linux Kernel repository, specifically in the commit b2aa2c4efe93e2580d6a8774b04fe2b99756a322.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
