Vulnerability in cpufreq: schedutil in Kernel
Summary
GSD-2021-1001516: cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory. Affects Kernel versions >= cb4a53ba37532c861a5f3f22803391018a41849a, < 1ba2e770481905b06f5684d6cbd0817a1432da2b. 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 system resources and facilitates communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The cpufreq subsystem within the Kernel is responsible for dynamically adjusting the CPU frequency to optimize power consumption and performance. One of the algorithms used in cpufreq is schedutil, which dynamically scales the CPU frequency based on the system load. However, a vulnerability has been discovered in the schedutil algorithm that can lead to memory corruption and potential security risks.
Vulnerability Detail
The vulnerability in cpufreq: schedutil arises from the improper handling of a mutex before freeing the associated memory. When the schedutil algorithm is used to adjust the CPU frequency, a mutex is acquired to ensure exclusive access to critical sections of code. However, in certain scenarios, the mutex is not properly destroyed before the memory associated with it is freed using kobject_put(). This can result in memory corruption and potential exploitation by malicious actors. 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
As a workaround, users can avoid using the schedutil algorithm for CPU frequency scaling and switch to alternative algorithms provided by the cpufreq subsystem. This can be achieved by modifying the Kernel configuration or using appropriate kernel boot parameters. However, it is strongly advised to apply the official fix by updating the Kernel to the latest version.
Conclusion
In conclusion, a vulnerability has been identified in the cpufreq: schedutil algorithm within the Kernel, which can lead to memory corruption and potential security risks. It is recommended to update the Kernel to version v4.9.285 or later to apply the official fix. Users can also use the Vulert Playground at https://vulert.com/scanner to check if their system is affected by this vulnerability. For further support on vulnerability remediation, please contact 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 memory corruption and potential security risks.
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 essential to apply the fix as soon as possible to mitigate any potential risks.
It is not recommended to manually patch the vulnerability without updating the Kernel. The official fix provided in the latest Kernel version ensures comprehensive mitigation of the vulnerability and is the recommended approach.
This vulnerability was introduced in Kernel version v4.9.285 by commit cb4a53ba37532c861a5f3f22803391018a41849a. Therefore, older versions of the Kernel may not be affected. However, it is still advisable to update to the latest stable version to ensure overall security.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
