Vulnerability in drm/msm/mdp5 Package: Return Error Code in mdp5_mixer_release when Deadlock is Detected
Summary
GSD-2022-1003408: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected. Affects Kernel versions >= 7907a0d77cb461f58045763c205a5830be72e97c, < 09bdeedc1fc53e64b8282e1de67752c69e43bdba. 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 on Qualcomm Snapdragon SoCs. It includes the mdp5_mixer_release function, which is responsible for releasing resources associated with a display mixer. The package is widely used in various Linux distributions and is critical for proper display functionality on devices utilizing Qualcomm Snapdragon processors.
Vulnerability Detail
The vulnerability in the drm/msm/mdp5 package allows for a deadlock condition to occur when releasing resources in the mdp5_mixer_release function. This can be exploited by an attacker to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges. The vulnerability was introduced in version v4.18 of the Linux Kernel and has been fixed in version v5.15.46.
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
As a workaround, users can avoid the vulnerability by not executing untrusted code or accessing untrusted content on systems running the affected versions of the Linux Kernel. Additionally, implementing proper access controls and restricting privileges for user accounts can help mitigate the risk of exploitation.
Conclusion
The vulnerability in the drm/msm/mdp5 package of the Linux Kernel can lead to a deadlock condition and potential code execution with elevated privileges. It is crucial to update the kernel to version v5.15.46 or later to mitigate the risk. Implementing proper access controls and exercising caution when executing untrusted code can also help protect against exploitation. For additional support, please reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a deadlock condition, resulting in a denial-of-service (DoS) or potential code execution with elevated privileges.
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 alerts for open-source vulnerabilities.
At the time of this report, there are no known public exploits targeting this specific vulnerability. However, it is important to apply the recommended fixes to mitigate the risk of potential exploitation.
Yes, this vulnerability can be exploited remotely if an attacker can execute malicious code on a system running the affected version of the Linux Kernel.
For further support and assistance with vulnerability remediation, you can contact info@devnack.com. They can provide guidance and resources to help address the issue.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.