Refcount Leak in drm/msm/mdp4

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004746: drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf. Affects Kernel versions >= 86418f90a4c1a0073db65d8a1e2bf94421117a60, < d1592d3e362cc59b29f15019707b16c695d70ca3. 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/mdp4 package is a component of the Linux Kernel that provides support for the display subsystem on Qualcomm Snapdragon SoCs. It includes the MDP4 (Mobile Display Processor 4) driver, which is responsible for managing the display interfaces and modesetting operations. The vulnerability in question is a refcount leak in the mdp4_modeset_init_intf function.

Vulnerability Detail

The refcount leak vulnerability in mdp4_modeset_init_intf can lead to a resource leak, potentially resulting in a denial of service (DoS) condition or memory exhaustion. The issue arises when the function fails to properly release a reference count on a display interface, causing the count to increment indefinitely. An attacker could exploit this vulnerability by repeatedly triggering the affected code path, leading to resource exhaustion and system instability.

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 essential to apply the provided fix by updating the Linux Kernel to the recommended version.

Conclusion

The refcount leak vulnerability in drm/msm/mdp4 can lead to resource exhaustion and system instability. It is crucial to update the Linux Kernel to version v5.4.202 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can lead to a denial of service (DoS) condition or memory exhaustion, potentially causing system instability.

An attacker can exploit this vulnerability by repeatedly triggering the affected code path, causing resource exhaustion and system instability.

Yes, a patch is available for this vulnerability. Users should update the Linux Kernel to version v5.4.202 or later.

No, this vulnerability was introduced in version v4.12 and fixed in version v5.4.202. Users should ensure they are running a version equal to or later than v5.4.202.

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