Vulnerability in cpufreq: schedutil in Kernel
Summary
GSD-2021-1001656: cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory. Affects Kernel versions >= a7d4fc84404d45d72f4490417e8cc3efa4af93f1, < 3945c481360caee7d496c95b5c73afe923a1c7cd. 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 components of cpufreq is schedutil, which implements the 'schedutil' governor for frequency scaling. This governor aims to adapt the CPU frequency based on the system's current workload. However, a vulnerability has been discovered in the schedutil component that could potentially lead to security issues.
Vulnerability Detail
The vulnerability in cpufreq: schedutil arises from a flaw in the handling of a mutex before freeing memory using kobject_put(). When the mutex is not destroyed before kobject_put() is called, it can result in memory being freed while still being accessed, leading to potential use-after-free vulnerabilities. An attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in Linux Kernel version v5.10.71 by commit a7d4fc84404d45d72f4490417e8cc3efa4af93f1 and has been fixed in version v5.10.71 by commit 3945c481360caee7d496c95b5c73afe923a1c7cd.
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 vulnerability in cpufreq: schedutil in the Kernel could potentially lead to security issues, including arbitrary code execution and denial-of-service. It is crucial to update the Linux Kernel to version v5.10.71 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to 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 condition.
You can use Vulert's playground at Vulert 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.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
The details regarding remote exploitation of this vulnerability have not been provided. However, it is always advisable to keep systems up to date with the latest security patches to minimize the risk of remote attacks.
The specific prerequisites for exploiting this vulnerability have not been mentioned. However, it is generally recommended to have local access to the system to exploit such vulnerabilities.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
