Memory Leak in imx_pd_connector_get_modes in drm/imx
Summary
GSD-2022-1001018: drm/imx: Fix memory leak in imx_pd_connector_get_modes. Affects Kernel versions >= 76ecd9c9fb24b014a6f33fbb1287ede3be12158b, < 7526102d908ec5ae777aa77723d52fce12916093. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The drm/imx module is a component of the Linux Kernel that provides support for display controllers on i.MX SoCs. It allows for the configuration and management of display modes and connectors. 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, which could 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 properly release allocated memory when an error condition occurs during the retrieval of display modes. This can result in a gradual accumulation of unreleased memory, leading to resource exhaustion and potential system instability. An attacker with access to this vulnerability could potentially exploit it to cause a denial-of-service (DoS) condition or other adverse effects on the affected system.
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 avoid triggering the error condition by refraining from performing actions that trigger the retrieval of display modes using the imx_pd_connector_get_modes function. However, this workaround may limit the functionality of the affected system and is not a permanent solution.
Conclusion
The memory leak vulnerability in imx_pd_connector_get_modes poses a risk of resource exhaustion and potential system instability. It is recommended to update the Linux Kernel to version v5.17.3 or later to mitigate this vulnerability. Users can also check their system's vulnerability status using the Vulert playground at https://vulert.com/scanner. For further assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a gradual accumulation of unreleased memory, potentially causing resource exhaustion and system instability. It could also be exploited by an attacker to cause a denial-of-service (DoS) condition.
You can check the version of the Linux Kernel installed on your system. If it is earlier than v5.17.3 and includes the affected drm/imx module, your system may be vulnerable.
At the time of this report, there are no known public exploits targeting this specific vulnerability. However, it is advisable to apply the recommended patch to mitigate the risk.
No, this vulnerability requires local access to the affected system in order to exploit it.
For more details about this vulnerability, including the specific commits that introduced and fixed it, you can refer to the provided references link.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
