Vulnerability in Kernel: i2c: cadence: 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

GSD-2021-1000357: i2c: cadence: fix reference leak when pm_runtime_get_sync fails. Affects Kernel versions >= 7fa32329ca03148fb2c07b4ef3247b8fc0488d6a, < 30410519328c94367e561fd878e5f0d3a0303585. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It includes various subsystems, including the i2c subsystem, which facilitates communication between integrated circuits. The Cadence i2c driver is responsible for managing i2c devices using Cadence controllers. This vulnerability specifically affects the Cadence i2c driver when the pm_runtime_get_sync function fails to acquire a reference. This reference leak can lead to resource exhaustion and potential system instability.

Vulnerability Detail

The vulnerability arises from a reference leak in the Cadence i2c driver when the pm_runtime_get_sync function fails. This reference leak can result in resource exhaustion, potentially leading to system instability or denial of service. The vulnerability was introduced in version v4.5 of the Linux Kernel and was fixed in version v5.10.37. The impact and attack plausibility of this vulnerability have not been proven.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.37 or later. This update includes the commit 30410519328c94367e561fd878e5f0d3a0303585, which addresses the reference leak issue. Users can obtain the updated Kernel from the official Linux Kernel repository.

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.

Conclusion

The vulnerability in the Cadence i2c driver can result in resource exhaustion and potential system instability. It is crucial to update the Linux Kernel to version v5.10.37 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can lead to resource exhaustion and potential system instability or denial of service.

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.

The actual impact and attack plausibility of this vulnerability have not yet been proven. However, it is always recommended to apply security updates to mitigate potential risks.

The details regarding remote exploitation of this vulnerability are not provided. However, it is advisable to keep systems up to date with the latest security patches to minimize the risk of remote attacks.

For more details about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.37 or later. This update includes the commit 30410519328c94367e561fd878e5f0d3a0303585, which addresses the reference leak issue. Users can obtain the updated Kernel from the official Linux Kernel repository.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.