Out-of-Bounds Issue in thermal/drivers/cpufreq_cooling
Summary
GSD-2021-1000052: thermal/drivers/cpufreq_cooling: Fix slab OOB issue. Affects Kernel versions >= 371a3bc79c11b707d7a1b7a2c938dc3cc042fffb, < 6bf443acf6ca4f666d0e4225614ba9993a3aa1a9. 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 part of the Linux Kernel, which is responsible for managing the thermal cooling devices and their frequency scaling. It provides a framework for controlling the CPU frequency based on the thermal conditions. The cpufreq_cooling driver specifically handles the cooling devices associated with the CPU frequency scaling. This vulnerability affects versions of the Linux Kernel from v5.8 to v5.12.2.
Vulnerability Detail
The vulnerability identified in thermal/drivers/cpufreq_cooling is an out-of-bounds (OOB) issue. It occurs due to improper handling of slab allocations, leading to potential memory corruption. An attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service (DoS) condition. 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
No specific workaround has been provided for this vulnerability.
Conclusion
In conclusion, the thermal/drivers/cpufreq_cooling module in the Linux Kernel is vulnerable to an out-of-bounds issue. This vulnerability can potentially lead to memory corruption and allow arbitrary code execution or cause a denial-of-service condition. It is crucial to update the Linux Kernel to version v5.12.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially allow an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
No known exploit has been reported for this vulnerability at the moment.
The recommended mitigation is to update the Linux Kernel to version v5.12.3 or later, which includes the fix for this vulnerability.
You can find more information about this vulnerability in the GSD-2021-1000052.json file available in the GSD database: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000052.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.