Vulnerability in Kernel: i2c: img-scb
Summary
GSD-2021-1000246: i2c: img-scb: fix reference leak when pm_runtime_get_sync fails. Affects Kernel versions >= 93222bd9b966105f43418fd336654ad10045783a, < 7ee35cde1e810ad6ca589980b9ec2b7b62946a5b. 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 manages communication between hardware and software. It provides essential functions and services to ensure the proper functioning of the system. The i2c (Inter-Integrated Circuit) subsystem within the Kernel enables communication between integrated circuits on a computer motherboard. The img-scb driver is responsible for managing the i2c controller on certain hardware platforms. However, a vulnerability has been identified in the img-scb driver that can lead to a reference leak when the pm_runtime_get_sync function fails.
Vulnerability Detail
The vulnerability in the img-scb driver occurs when the pm_runtime_get_sync function fails to acquire a reference. This can result in a reference leak, leading to resource exhaustion and potential system instability. An attacker may be able to exploit this vulnerability to cause a denial-of-service condition or potentially execute arbitrary code with elevated privileges. The vulnerability was introduced in version v4.15 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 recommended to apply the fix mentioned in the 'how_to_fix' section.
Conclusion
The vulnerability in the Kernel's i2c img-scb driver can result in a reference leak, leading to resource exhaustion and potential system instability. It is crucial to update the Linux Kernel to version v5.12.4 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to a denial-of-service condition or potential code execution with elevated privileges.
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 and it will provide real-time alerts for open-source vulnerabilities.
The exact attack vector for this vulnerability is not specified. However, it is possible that an attacker with remote access to the system could exploit this vulnerability.
There is no evidence of this vulnerability being actively exploited at the moment. However, it is recommended to apply the fix as soon as possible to mitigate any potential risks.
The only known mitigation for this vulnerability is to update the Linux Kernel to version v5.12.4 or later.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
