Vulnerability in drm/msm/mdp5 Package: Return Error Code in mdp5_mixer_release when Deadlock is Detected
Summary
GSD-2022-1003117: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected. Affects Kernel versions >= 7907a0d77cb461f58045763c205a5830be72e97c, < 47e393061049aff6818d1b9fdca7351411a23fc2. 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 ecosystem. It provides support for display controllers found in Qualcomm Snapdragon SoCs. The package includes the mdp5_mixer_release function, which is responsible for releasing a mixer resource. This function is vulnerable to a deadlock issue when certain conditions are met.
Vulnerability Detail
The vulnerability arises from a failure to return an error code in the mdp5_mixer_release function when a deadlock is detected. This can lead to a situation where the resource is not properly released, potentially causing resource leaks and other issues. The vulnerability was introduced in version v4.18 of the Linux Kernel and has been fixed in version v5.17.14.
How To Fix
No fixed version is published for this vulnerability.
To fix this vulnerability, it is recommended to update to the latest version of the Linux Kernel (v5.17.14 or later). This can be done by obtaining the updated kernel source code and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated package that includes the fix.
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 drm/msm/mdp5 package in the Linux Kernel is vulnerable to a deadlock issue in the mdp5_mixer_release function. This vulnerability can lead to resource leaks and other issues. It is recommended to update to the latest version of the Linux Kernel to fix 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 and other issues due to the improper release of a mixer resource.
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 and the tool will analyze it for vulnerabilities.
There is no known exploit for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
The vulnerability itself does not provide remote code execution capabilities. However, if an attacker already has access to the system, they may be able to leverage this vulnerability to escalate their privileges or cause other issues.
The recommended solution is to update to the latest version of the Linux Kernel. However, if updating is not feasible, you can consider implementing additional security measures such as restricting access to the affected component or implementing runtime checks to detect and handle potential deadlock situations.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.