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

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003910: drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected. Affects Kernel versions >= 7907a0d77cb461f58045763c205a5830be72e97c, < 776f5c58bfe16cf322d71eeed3c5dda1eeac7e6b. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The drm/msm/mdp5 package is a component of the Linux Kernel that provides support for display controllers in Qualcomm Snapdragon SoCs. It is responsible for managing the display pipelines and handling various operations related to graphics rendering and output. The mdp5_pipe_release function within this package is used to release 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 a deadlock is detected during the release of a display pipeline using the mdp5_pipe_release function. In such cases, the function fails to return an error code, which can result in incorrect behavior or unexpected system behavior. An attacker may be able to exploit this vulnerability to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.19.247 or later. This update includes a commit (776f5c58bfe16cf322d71eeed3c5dda1eeac7e6b) that addresses the issue. Users should ensure that they are running a version of the Linux Kernel that includes this fix.

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 at this time.

Conclusion

In conclusion, the drm/msm/mdp5 package in the Linux Kernel is vulnerable to a deadlock condition when releasing a display pipeline. This can result in unexpected system behavior or potentially allow an attacker to execute arbitrary code with elevated privileges. It is crucial to update the kernel to version v4.19.247 or later to address this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a deadlock condition and may allow an attacker to cause a denial-of-service (DoS) or 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 tool will provide real-time alerts for open-source vulnerabilities.

There are no known exploits for this vulnerability at this time.

Yes, a patch is available in the Linux Kernel version v4.19.247. Users should update their kernel to this version or later to mitigate the vulnerability.

No, updating the kernel to the patched version is the recommended way to mitigate this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.19.247 or later. This update includes a commit (776f5c58bfe16cf322d71eeed3c5dda1eeac7e6b) that addresses the issue. Users should ensure that they are running a version of the Linux Kernel that includes this fix.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.