Vulnerability in Kernel: i2c: cadence: fix reference leak when pm_runtime_get_sync fails
Summary
GSD-2021-1000247: i2c: cadence: fix reference leak when pm_runtime_get_sync fails. Affects Kernel versions >= 7fa32329ca03148fb2c07b4ef3247b8fc0488d6a, < a45fc41beed8e0fe31864619c34aa00797fb60c1. 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 Kernel is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. The i2c subsystem in the Kernel facilitates communication between integrated circuits, allowing devices to exchange data. The Cadence i2c driver is responsible for managing i2c devices using Cadence IP. However, a vulnerability has been identified in the Cadence i2c driver that can lead to a reference leak when the pm_runtime_get_sync function fails.
Vulnerability Detail
The vulnerability in the Cadence i2c driver occurs when the pm_runtime_get_sync function fails to acquire a reference. This reference leak can result in a resource exhaustion condition, leading to potential denial-of-service attacks or other security implications. Attackers may be able to exploit this vulnerability to cause system instability or crash the system. The vulnerability was introduced in version v4.5 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 →
Workaround
There is no specific workaround available for this vulnerability. It is advised to apply the recommended fix by updating the Linux Kernel to the latest version.
Conclusion
The vulnerability in the Cadence i2c driver can lead to resource exhaustion and potential denial-of-service attacks. It is crucial to update the Linux Kernel to version v5.12.4 or later to address this vulnerability. By applying the recommended fix, the system will be protected against potential exploitation. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to denial-of-service attacks or system instability. Attackers may be able to exploit the reference leak to exhaust system resources or crash the 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 without requiring access to the code or installation.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
This vulnerability can potentially be exploited remotely if an attacker can gain access to the affected system. It is crucial to update the Linux Kernel to the latest version to prevent any remote exploitation.
The recommended solution is to update the Linux Kernel to the latest version. There are no known alternative solutions to fix this specific vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
