Vulnerability in drm/msm/mdp5 Package: Return Error Code in mdp5_pipe_release when Deadlock is Detected
Summary
GSD-2022-1003122: drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected. Affects Kernel versions >= 7907a0d77cb461f58045763c205a5830be72e97c, < 19964dfb39bda4d7716a71009488f0668ecbcf52. 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 in Qualcomm Snapdragon processors. It is responsible for managing the display pipelines and ensuring the proper rendering of graphics on the screen. The mdp5_pipe_release function in this package is used to release resources associated with a display pipeline. However, a vulnerability has been discovered in this function that can lead to a deadlock condition.
Vulnerability Detail
The vulnerability arises when the mdp5_pipe_release function fails to return an error code when a deadlock is detected. This can occur if there is a circular dependency between display pipelines, causing a deadlock situation. An attacker could exploit this vulnerability by triggering the deadlock condition, leading to a denial of service (DoS) or potentially allowing for the execution of arbitrary code. 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.
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_pipe_release function. This vulnerability can lead to a denial of service (DoS) or potential code execution. It is crucial to update the Linux Kernel to version v5.17.14 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 a denial of service (DoS) condition or potentially allow for the execution of arbitrary code.
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 Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if an attacker can trigger the deadlock condition on a vulnerable system.
There is no evidence of this vulnerability being actively exploited in the wild. However, it is always recommended to apply security patches and updates to protect against potential threats.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
