Vulnerability in drm/msm/mdp5 Package: Return Error Code in mdp5_mixer_release when Deadlock is Detected
Summary
GSD-2022-1002774: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected. Affects Kernel versions >= 7907a0d77cb461f58045763c205a5830be72e97c, < 46e5ce63924a96af452c4fc5ee0bb3b241e1b9f4. 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 controllers found in Qualcomm Snapdragon SoCs. It is responsible for managing the display pipeline and handling various operations related to graphics rendering and output. The mdp5_mixer_release function within this package is used to release resources associated with a display mixer. However, a vulnerability has been discovered in this function that can lead to a deadlock condition.
Vulnerability Detail
The vulnerability arises when a deadlock is detected during the execution of the mdp5_mixer_release function. In such cases, the function should return an error code to indicate the deadlock. However, the affected versions of the drm/msm/mdp5 package do not properly handle this situation and fail to return an error code. This can result in incorrect behavior or system instability. The vulnerability was introduced in version v4.18 of the Linux Kernel and has been fixed in version v5.18.3.
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 drm/msm/mdp5 package in the Linux Kernel is vulnerable to a deadlock condition in the mdp5_mixer_release function. This vulnerability can result in incorrect behavior or system instability. It is recommended to update the Linux Kernel to version v5.18.3 or later to fix this issue. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to incorrect behavior or system instability, potentially affecting the overall functionality and reliability of the system.
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 analyze the dependencies and alert you if any vulnerabilities are found.
At the time of this report, there are no known exploits for this vulnerability. However, it is always recommended to apply security patches promptly to mitigate the risk of potential exploits.
While it is technically possible to manually patch the affected function, it is not recommended unless you have a deep understanding of the Linux Kernel and the specific code changes required. It is safer and more convenient to update the entire Linux Kernel to the fixed version.
You can find more information about this vulnerability in the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and the vulnerability database maintained by the Cloud Security Alliance (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
