Vulnerability in cpufreq: schedutil in Kernel
Summary
GSD-2021-1001537: cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory. Affects Kernel versions >= 463c46705f321201090b69c4ad5da0cd2ce614c9, < 514643eadfeab8ee11e55981289c720308eb0afd. 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 Kernel is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. The cpufreq subsystem within the Kernel is responsible for dynamically adjusting the CPU frequency to optimize performance and power consumption. One of the modules in cpufreq, schedutil, implements a governor that utilizes the Linux scheduler to make frequency scaling decisions. However, a vulnerability has been identified in schedutil that could lead to memory corruption and potential security risks.
Vulnerability Detail
The vulnerability in cpufreq: schedutil arises from the improper destruction of a mutex before the associated memory is freed by kobject_put(). This flaw can be exploited by an attacker to manipulate the mutex state after it has been freed, leading to memory corruption and potentially enabling arbitrary code execution or privilege escalation. The impact and attack plausibility of this vulnerability have not been proven yet, but it is crucial to address it to ensure the security and stability of the system.
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 governor in the cpufreq subsystem. Instead, they can switch to alternative governors like performance or powersave. This can be achieved by modifying the system configuration or using tools like cpufrequtils to change the governor settings. By avoiding the use of schedutil, the vulnerability can be circumvented until the Kernel is updated.
Conclusion
The vulnerability in cpufreq: schedutil in the Kernel poses a potential risk of memory corruption and arbitrary code execution. It is crucial to update the Linux Kernel to version v4.14.249 or later to fix this vulnerability. In the meantime, users can employ the workaround of avoiding the use of schedutil governor and switching to alternative governors. 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 could potentially lead to memory corruption, enabling arbitrary code execution or privilege escalation. However, the actual impact and attack plausibility have not been proven yet.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
Yes, a fix for this vulnerability is available in Linux Kernel version v4.14.249 or later. It is recommended to update the Kernel to ensure the security of the system.
Yes, you can avoid using the schedutil governor in the cpufreq subsystem as a workaround. Switching to alternative governors like performance or powersave can help mitigate the risk until the Kernel is updated.
You can find more information about this vulnerability in the Open Source Vulnerability database maintained by the Cloud Security Alliance. The vulnerability ID is GSD-2021-1001537.
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.
