Refcount Leak in imx_sc_thermal_probe in Kernel
Summary
GSD-2022-1002742: thermal/drivers/imx_sc_thermal: Fix refcount leak in imx_sc_thermal_probe. Affects Kernel versions >= e20db70dba1c0783b9878ce37171ad560b1ebaf3, < ec0925b731697db7cab5944a3e55d2d58bb3d075. 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 the system's resources and facilitates communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The imx_sc_thermal_probe is a thermal driver in the Kernel specifically designed for the i.MX System Controller (SC) thermal sensor. This driver is responsible for monitoring the temperature of the i.MX SoC and taking appropriate actions to prevent overheating. However, a vulnerability has been identified in the imx_sc_thermal_probe driver that can lead to a refcount leak.
Vulnerability Detail
The refcount leak vulnerability in the imx_sc_thermal_probe driver allows an attacker to cause a memory leak by repeatedly probing the thermal sensor. This can result in a gradual depletion of system memory, leading to performance degradation or even a denial of service condition. The vulnerability was introduced in version v5.7 of the Linux Kernel and was fixed in version v5.18.3. The impact and attack plausibility of this vulnerability have not been proven yet.
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 refcount leak vulnerability in the imx_sc_thermal_probe driver of the Linux Kernel can lead to memory depletion and potential performance degradation. It is crucial to update the Kernel to version v5.18.3 or later to fix this vulnerability. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in a gradual depletion of system memory, leading to performance degradation or even a denial of service condition.
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.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
The details regarding remote exploitation have not been provided. It is advisable to keep the Kernel up to date to minimize the risk of any potential remote attacks.
The recommended solution is to update the Linux Kernel to the latest version. However, if updating is not feasible, you can consider implementing additional security measures such as network segmentation and access controls to mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
