Memory Leak Vulnerability in thermal: int340x
Summary
GSD-2022-1000792: thermal: int340x: fix memory leak in int3400_notify(). Affects Kernel versions >= 38e44da591303d08b0d965a033e11ade284999d0, < ba9efbbf6745750d34c1e87c9539ce9db645ca0a. 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 thermal package is a component of the Linux Kernel that manages thermal events and controls the thermal behavior of devices. It provides a framework for thermal management and includes drivers for various thermal sensors and cooling devices. The int340x driver is specifically responsible for handling thermal events on Intel platforms. This vulnerability affects the int340x driver and can lead to a memory leak.
Vulnerability Detail
The vulnerability in the int340x driver of the thermal package allows for a memory leak in the int3400_notify() function. When certain thermal events occur, memory is allocated but not properly freed, leading to a memory leak. This can result in a gradual depletion of available memory resources, potentially causing system instability or denial of service. The vulnerability was introduced in version v4.14 of the Linux Kernel and has been fixed in version v5.15.26.
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. However, users can mitigate the risk by regularly updating their Linux Kernel to the latest stable version.
Conclusion
The memory leak vulnerability in the thermal: int340x driver of the Linux Kernel can lead to system instability or denial of service. Users should update their kernel to version v5.15.26 or later to fix the vulnerability. Regularly updating the Linux Kernel to the latest stable version is also advised to mitigate any potential security risks. 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 system instability or denial of service.
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 the playground will analyze it for any open-source vulnerabilities, including this one.
Yes, the vulnerability has been fixed in version v5.15.26 of the Linux Kernel. Users should update their kernel to this version or later to apply the patch.
No, the recommended fix is to update the Linux Kernel to the patched version. Manually fixing the vulnerability without updating the kernel may not be feasible or effective.
At the time of this report, there are no known exploits for this vulnerability. However, it is always recommended to apply security patches promptly to mitigate any potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
