Vulnerability in Kernel: i2c: img-scb
Summary
GSD-2021-1000356: i2c: img-scb: fix reference leak when pm_runtime_get_sync fails. Affects Kernel versions >= 93222bd9b966105f43418fd336654ad10045783a, < e80ae8bde41266d3b8bf012460b6593851766006. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a crucial component of the Linux operating system, responsible for managing system resources and providing an interface between hardware and software. The i2c (Inter-Integrated Circuit) subsystem within the Kernel enables communication between integrated circuits on a computer motherboard. The img-scb driver is specifically used for handling I2C transactions on certain platforms. However, a vulnerability has been discovered in this driver that could lead to a reference leak when the pm_runtime_get_sync function fails.
Vulnerability Detail
The vulnerability in the i2c: img-scb driver occurs when the pm_runtime_get_sync function fails. This failure can result in a reference leak, which can lead to resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability to exhaust system resources, causing the system to become unresponsive or crash. The vulnerability was introduced in version v4.15 of the Linux Kernel and has been fixed in version v5.10.37.
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.
Conclusion
The vulnerability in the i2c: img-scb driver can result in a reference leak when the pm_runtime_get_sync function fails. This can lead to resource exhaustion and potential denial-of-service attacks. 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, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and potential denial-of-service attacks. An attacker could exploit this vulnerability to exhaust system resources, causing the system to become unresponsive or crash.
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 to the playground, and it will alert you if the vulnerability is present.
Yes, a patch is available in version v5.10.37 of the Linux Kernel. It is recommended to update to this version or later to fix the vulnerability.
The details of remote exploitation have not been provided in the vulnerability report. However, it is always recommended to apply security updates promptly to mitigate potential risks.
There is no information available regarding known instances of this vulnerability being exploited in the wild. However, it is important to apply the recommended updates to ensure the security of your system.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
