Vulnerability in Kernel: i2c: imx: fix reference leak when pm_runtime_get_sync fails

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

UVI-2021-1000354: i2c: imx: fix reference leak when pm_runtime_get_sync fails. Affects Kernel versions >= 3a5ee18d2a32bda6b9a1260136f6805848e3839d, < 3a0cdd336d92c429b51a79bf4f64b17eafa0325d. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Kernel is a critical component of the Linux operating system that manages communication between hardware and software. It provides essential functions and services to enable the proper functioning of the system. The i2c subsystem in the Kernel is responsible for handling communication with I2C devices, such as sensors and other peripherals. The i2c-imx driver specifically supports I2C communication on i.MX platforms. This vulnerability in the i2c-imx driver can lead to a reference leak when the pm_runtime_get_sync function fails. This reference leak can result in resource exhaustion and potential system instability.

Vulnerability Detail

The vulnerability arises from a reference leak in the i2c-imx driver when the pm_runtime_get_sync function fails. This leak can occur when the driver attempts to acquire a reference to a device and fails to release it properly in case of a failure. As a result, the reference count for the device is not decremented, leading to a resource leak. An attacker could potentially exploit this vulnerability to exhaust system resources, leading to a denial-of-service condition or other forms of system instability. The impact and attack plausibility of this vulnerability have not been proven yet.

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 specific workaround mentioned for this vulnerability. However, users can mitigate the risk by following best practices for system security, such as ensuring the Kernel is up to date with the latest stable version and implementing proper access controls to limit potential attack vectors.

Conclusion

The vulnerability in the i2c-imx driver can lead to a reference leak when the pm_runtime_get_sync function fails. This can result in resource exhaustion and potential system instability. It is crucial to update the Kernel to a version that includes the fix for this vulnerability to mitigate the risk. Regularly updating the Kernel is recommended to ensure the presence of security patches and bug fixes. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can potentially lead to resource exhaustion and system instability, which may result in a denial-of-service condition or other adverse effects on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just a manifest file like package-lock.json.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the necessary updates and security patches to mitigate the risk.

The details regarding remote exploitation of this vulnerability are not provided. However, it is always recommended to keep systems updated and apply security best practices to minimize the risk of remote exploitation.

If your system is affected, it is recommended to update the Kernel to a version that includes the fix for this vulnerability. Regularly updating the Kernel to the latest stable version is advisable to ensure the presence of security patches and bug fixes.

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