Memory Leak in drm/imx_pd_connector_get_modes

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002309: drm/imx: Fix memory leak in imx_pd_connector_get_modes. Affects Kernel versions >= 76ecd9c9fb24b014a6f33fbb1287ede3be12158b, < 41624d7c0c3df71dee170c610744aaa5909327b8. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The drm/imx_pd_connector_get_modes function is part of the Linux Kernel package, which is responsible for managing the core functionality of the Linux operating system. This particular function is used in the i.MX platform driver to retrieve the supported display modes for a given connector. The i.MX platform is widely used in embedded systems and IoT devices. However, a memory leak vulnerability has been identified in the imx_pd_connector_get_modes function, which could lead to resource exhaustion and potential system instability.

Vulnerability Detail

The memory leak vulnerability in imx_pd_connector_get_modes arises from a failure to properly release allocated memory when retrieving display modes. This can result in a gradual accumulation of unreleased memory, leading to resource exhaustion and potential system crashes. An attacker with local access to the affected system could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition. The vulnerability was introduced in Linux Kernel version v4.8 and has been fixed in version v4.19.238.

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 temporary workaround, users can disable the affected functionality by blacklisting the imx_pd_connector_get_modes function. This can be achieved by modifying the kernel configuration or using kernel module parameters. However, it is important to note that this workaround may result in limited or degraded display functionality.

Conclusion

The memory leak vulnerability in drm/imx_pd_connector_get_modes can lead to resource exhaustion and potential system crashes. It is crucial to update the Linux Kernel package to version v4.19.238 or later to mitigate this vulnerability. Alternatively, users can apply the temporary workaround of blacklisting the affected function, although this may result in limited display functionality. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to resource exhaustion and potential system crashes, potentially causing a denial-of-service (DoS) condition.

Users of Linux systems running the affected versions of the Linux Kernel package, specifically those utilizing the i.MX platform driver.

No, this vulnerability requires local access to the affected system in order to be exploited.

There are no known instances of this vulnerability being exploited in the wild at this time.

Yes, the vulnerability has been fixed in Linux Kernel version v4.19.238. Users are advised to update to this version or later.

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