Vulnerability in drm/msm/mdp5 Package: Return Error Code in mdp5_mixer_release when Deadlock is Detected

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003911: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected. Affects Kernel versions >= 7907a0d77cb461f58045763c205a5830be72e97c, < 1a5d1474026ea4f1a6f931075ca2adb884af39cf. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The drm/msm/mdp5 package is a component of the Linux Kernel that provides support for display controllers on 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 the mdp5_mixer_release function encounters a deadlock situation. In such cases, the function fails to return an error code, which can result in incorrect behavior and potential system instability. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition or execute arbitrary code with elevated privileges. The vulnerability was introduced in version v4.18 of the Linux Kernel and has been fixed in version v4.19.247.

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 triggering the deadlock condition by refraining from performing certain actions that may lead to it. However, this workaround may not be feasible in all scenarios and it is strongly recommended to apply the official 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 lead to a denial-of-service (DoS) condition or arbitrary code execution. It is crucial to update the Linux Kernel to version v4.19.247 or later to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially lead to a denial-of-service (DoS) condition or allow an attacker to execute arbitrary code 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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

Yes, a patch has been released in version v4.19.247 of the Linux Kernel. It is recommended to update to this version or a later one to fix the vulnerability.

While refraining from triggering the deadlock condition can serve as a temporary workaround, it is strongly advised to apply the official fix by updating the Linux Kernel as soon as possible.

There are no known instances of this vulnerability being exploited in the wild. However, it is important to apply the fix promptly to ensure the security and stability of your system.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback