Memory Leak in imx_pd_connector_get_modes in drm/imx
Summary
GSD-2022-1001982: drm/imx: Fix memory leak in imx_pd_connector_get_modes. Affects Kernel versions >= 76ecd9c9fb24b014a6f33fbb1287ede3be12158b, < f8b0ef0a5889890b50482b6593bd8de544736351. 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 package is a component of the Linux Kernel that provides support for display controllers on i.MX SoCs. It is responsible for managing the display modes and configurations for devices using the i.MX platform. The imx_pd_connector_get_modes function in this package is used to retrieve 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 cause a denial of service (DoS) condition by repeatedly calling the function with specially crafted input. Each call to the function results in a small memory allocation that is not properly freed, leading to a gradual depletion of available memory. This can eventually cause the system to become unresponsive or crash. The vulnerability was introduced in version v4.8 of the Linux Kernel and has been fixed in version v5.10.111.
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 necessary to update the Linux Kernel to the fixed version.
Conclusion
In conclusion, the memory leak vulnerability in imx_pd_connector_get_modes can lead to a denial of service (DoS) condition. It is recommended to update the Linux Kernel to version v5.10.111 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial of service (DoS) condition, causing the system to become unresponsive or crash.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability without requiring access to the code or installation.
No, there is no known workaround. It is necessary to update the Linux Kernel to the fixed version.
The vulnerability was introduced in version v4.8 of the Linux Kernel and has been fixed in version v5.10.111.
You can find more information about this vulnerability in the GSD-2022-1001982 JSON report available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001982.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
