Memory Leak in imx_pd_connector_get_modes in drm/imx

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001361: drm/imx: Fix memory leak in imx_pd_connector_get_modes. Affects Kernel versions >= 76ecd9c9fb24b014a6f33fbb1287ede3be12158b, < bc23c327e1a23cc3555fa1e86288e13288515442. 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/imx module is a component of the Linux Kernel that provides support for graphics and display functionality on i.MX SoCs. It includes drivers for various display connectors, such as HDMI and LVDS. The imx_pd_connector_get_modes function is responsible for retrieving the supported display modes for a given connector. However, a memory leak vulnerability has been identified in this function.

Vulnerability Detail

The memory leak vulnerability in imx_pd_connector_get_modes allows an attacker to exhaust system memory by repeatedly calling the function without releasing the allocated memory. This can lead to a denial of service (DoS) condition, as the system may become unresponsive or crash due to insufficient memory. The vulnerability was introduced in version v4.8 of the Linux Kernel and is fixed in version v5.16.20.

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 v5.16.20 or later. This can be done by downloading the latest kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated package containing the fixed version of the kernel.

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

The memory leak vulnerability in imx_pd_connector_get_modes can result in a denial of service (DoS) condition by exhausting system memory. It is crucial to update the Linux Kernel to version v5.16.20 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

The vulnerability can lead to a denial of service (DoS) condition, as the system may become unresponsive or crash due to memory exhaustion.

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 any known vulnerabilities.

At the time of this report, there is no known exploit for this vulnerability. However, it is still recommended to apply the fix as soon as possible to prevent any potential attacks.

No, this vulnerability requires local access to the system in order to exploit it.

The only mitigation for this vulnerability is to apply the fix by updating the Linux Kernel to the fixed version.

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 v5.16.20 or later. This can be done by downloading the latest kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated package containing the fixed version of the kernel.

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.