Vulnerability in i2c: imx-lpi2c Package
Summary
GSD-2021-1000245: i2c: imx-lpi2c: fix reference leak when pm_runtime_get_sync fails. Affects Kernel versions >= 13d6eb20fc79a1e606307256dad4098375539a09, < b100650d80cd2292f6c152f5f2943b5944b3e8ce. 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 i2c: imx-lpi2c package is a component of the Linux Kernel ecosystem. It provides support for the Inter-Integrated Circuit (I2C) bus on i.MX processors. The I2C bus is a widely used serial communication protocol for connecting low-speed peripherals to microcontrollers and embedded systems. The imx-lpi2c driver is responsible for managing the I2C bus on i.MX processors. It allows devices connected to the bus to communicate with the processor. However, a vulnerability has been identified in this package that can lead to a reference leak when the pm_runtime_get_sync function fails.
Vulnerability Detail
The vulnerability in the i2c: imx-lpi2c package occurs when the pm_runtime_get_sync function fails. This function is responsible for managing the power state of the device. When the function fails, it results in a reference leak, which can lead to resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability by repeatedly triggering the failure of the pm_runtime_get_sync function, causing the system to exhaust its resources and become unresponsive. This vulnerability was introduced in version v4.16 of the Linux Kernel and has been fixed in version v5.12.4.
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 →
Conclusion
The i2c: imx-lpi2c package in the Linux Kernel is vulnerable to a reference leak issue when the pm_runtime_get_sync function fails. This vulnerability can lead to resource exhaustion and potential denial-of-service attacks. It is recommended to update the Linux Kernel to version v5.12.4 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability to render the system unresponsive.
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 to the playground, and it will analyze the dependencies and alert you if any vulnerabilities are found.
No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network.
There are no known instances of this vulnerability being exploited in the wild at this time.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
