Memory Leak in thermal/core Package
Summary
GSD-2022-1003596: thermal/core: Fix memory leak in __thermal_cooling_device_register(). Affects Kernel versions >= 8ea229511e06f9635ecc338dcbe0db41a73623f0, < 18530bedd221160823f63ccc20dd55c7a03edbcf. 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 thermal/core package is a component of the Linux Kernel that manages thermal cooling devices. It provides a framework for registering and controlling cooling devices to prevent overheating of hardware components. The package is responsible for allocating and releasing memory resources for cooling devices. However, a memory leak vulnerability has been identified in the __thermal_cooling_device_register() function.
Vulnerability Detail
The vulnerability in the thermal/core package is caused by a memory leak in the __thermal_cooling_device_register() function. When a cooling device is registered, memory is allocated for its data structure. However, if the registration fails, the allocated memory is not properly released, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, resulting in a denial-of-service condition. The vulnerability was introduced in version v4.17 of the Linux Kernel and has been fixed in version v5.10.121.
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 apply the fix by updating the Linux Kernel to the recommended version.
Conclusion
The memory leak vulnerability in the thermal/core package of the Linux Kernel can be mitigated by updating to version v5.10.121 or later. It is crucial to apply the fix to prevent potential denial-of-service attacks caused by memory exhaustion. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a memory leak, potentially causing a denial-of-service condition by exhausting system memory resources.
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 provide real-time alerts for open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the fix to prevent potential exploitation.
No, manual memory release is not recommended as it may lead to instability or other issues. It is best to update the Linux Kernel to the fixed version.
The recommended solution is to update the Linux Kernel to the fixed version. Alternative solutions may not provide complete mitigation or may introduce other compatibility issues.
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.
