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-1001687: drm/imx: Fix memory leak in imx_pd_connector_get_modes. Affects Kernel versions >= 76ecd9c9fb24b014a6f33fbb1287ede3be12158b, < 31e449302ed00c38d4068443cf0243279701ab28. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The drm/imx module is a component of the Linux Kernel that provides support for display controllers found in i.MX SoCs. It enables the management and configuration of display connectors, modes, and related functionality. The imx_pd_connector_get_modes function is responsible for retrieving the supported display modes for a given connector. However, a memory leak vulnerability exists in this function, which can lead to the exhaustion of system resources over time.

Vulnerability Detail

The memory leak vulnerability in imx_pd_connector_get_modes arises from a failure to release allocated memory when an error condition occurs during the retrieval of display modes. This can result in a gradual depletion of available memory, potentially leading to system instability or denial of service. The vulnerability was introduced in version v4.8 of the Linux Kernel and was fixed in version v5.15.34. The impact and attack plausibility of this vulnerability have not been proven.

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 the memory leak by refraining from using the imx_pd_connector_get_modes function or by implementing their own memory release mechanism after calling the function. However, it is strongly advised to apply the official fix by updating the Linux Kernel to the recommended version.

Conclusion

The memory leak vulnerability in imx_pd_connector_get_modes can pose a risk to system stability and availability. It is crucial to update the Linux Kernel to version v5.15.34 or later, which includes the necessary fix. Users can also consider implementing the provided workaround until the update is applied. Regularly checking for vulnerability alerts and utilizing tools like Vulert can help ensure the timely detection and mitigation of open-source vulnerabilities.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The memory leak vulnerability in imx_pd_connector_get_modes can lead to the gradual depletion of system resources, potentially resulting in system instability or denial of service.

Users can check their Linux Kernel version and compare it to the affected and fixed versions mentioned in the vulnerability details. Additionally, vulnerability scanning tools like Vulert can provide real-time alerts for open-source vulnerabilities.

At the time of this report, no known exploits for this vulnerability have been documented. However, it is important to apply the recommended fix to mitigate any potential risks.

The remote exploitability of this vulnerability has not been proven. However, it is always advisable to keep systems up to date with the latest security patches to minimize potential risks.

For further support and assistance in addressing this vulnerability, please contact info@devnack.com.

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