Vulnerability in Kernel: i2c: sprd: 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-1000244: i2c: sprd: fix reference leak when pm_runtime_get_sync fails. Affects Kernel versions >= 8b9ec0719834fe66146d138d62ed66cef025c864, < d3406ab52097328a3bc4cbe124bfd8f6d51fb86f. 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 for the proper functioning of the system. The i2c subsystem in the Kernel is responsible for handling communication with I2C devices, which are commonly used for connecting various peripherals. The sprd driver within the i2c subsystem is specifically designed for Spreadtrum SoCs. This driver allows communication with I2C devices on Spreadtrum-based systems. However, a vulnerability has been discovered in the sprd driver that can lead to a reference leak when the pm_runtime_get_sync function fails.

Vulnerability Detail

The vulnerability in the sprd driver occurs when the pm_runtime_get_sync function fails to acquire a reference. This can happen due to various reasons, such as an error in the device power management or resource allocation. When the function fails, it should release any acquired references to prevent resource leaks. However, in this case, the reference is not properly released, leading to a reference leak. This vulnerability can result in resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability to exhaust system resources, causing instability or crashes.

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 essential to update the Kernel to the fixed version to mitigate the risk of exploitation.

Conclusion

The vulnerability in the sprd driver of the Kernel can lead to a reference leak when the pm_runtime_get_sync function fails. This can result in resource exhaustion and potential denial-of-service attacks. To mitigate this vulnerability, it is crucial to update the Kernel to version v5.12.4 or later. There is no known workaround for this issue. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can lead to resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability to exhaust system resources, causing instability or crashes.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to update the Kernel to the fixed version to prevent potential exploitation.

No, there is no known workaround for this vulnerability. Updating the Kernel to the fixed version is the recommended solution.

You can find more information about this vulnerability in the official Linux Kernel repository at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/.

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