Out-of-Bounds Issue in thermal/drivers/cpufreq_cooling
Summary
GSD-2021-1000092: thermal/drivers/cpufreq_cooling: Fix slab OOB issue. Affects Kernel versions >= 371a3bc79c11b707d7a1b7a2c938dc3cc042fffb, < 876a5f33e5d961d879c5436987c09b3d9ef70379. 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/drivers/cpufreq_cooling module is a component of the Linux Kernel that manages the cooling devices for CPUs based on their frequency. It provides a mechanism to dynamically adjust the cooling policy based on the CPU frequency. This module is vulnerable to an out-of-bounds (OOB) issue, which can potentially lead to security vulnerabilities.
Vulnerability Detail
The OOB issue in thermal/drivers/cpufreq_cooling arises due to a flaw in the code implementation. An attacker could exploit this vulnerability to gain unauthorized access or execute arbitrary code on the affected system. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in Linux Kernel version v5.8 and has been fixed in version v5.11.20.
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 out-of-bounds issue in thermal/drivers/cpufreq_cooling can pose a potential security risk if exploited. It is crucial to update the Linux Kernel to version v5.11.20 or later to mitigate 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 impact of this vulnerability is not yet proven. However, if successfully exploited, it could lead to unauthorized access or arbitrary code execution on the affected system.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It provides real-time monitoring and alerts for open-source vulnerabilities without requiring access to the code or installation.
Yes, the vulnerability has been fixed in Linux Kernel version v5.11.20. It is recommended to update to this version or later to mitigate the risk.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to prevent any potential attacks.
You can refer to the official Linux Kernel documentation and the vulnerability database maintained by the Cloud Security Alliance (CSA) for more details about this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
