Vulnerability in cpufreq: schedutil in Kernel
Summary
GSD-2021-1001734: cpufreq: schedutil: Use kobject release() method to free sugov_tunables. Affects Kernel versions >= 9bdcb44e391da5c41b98573bf0305a0e0b1c9569, < 8d62aec52a8c5b1d25a2364b243fcc5098a2ede9. 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 package is an essential component of the Linux operating system. It provides core functionalities and acts as a bridge between the hardware and software layers. The cpufreq subsystem within the Kernel allows for dynamic frequency scaling of the CPU, optimizing performance and power consumption. The schedutil governor is responsible for making frequency decisions based on the CPU's utilization. However, a vulnerability has been discovered in the schedutil governor that can lead to potential security risks.
Vulnerability Detail
The vulnerability in cpufreq: schedutil arises from the improper handling of memory resources. Specifically, the sugov_tunables structure is not correctly freed, which can result in memory leaks and potential exploitation by malicious actors. Although the impact and attack plausibility have not been proven, this vulnerability should be addressed to ensure the stability and security of the system. The vulnerability was introduced in version v4.7 of the Linux Kernel and has been fixed in version v5.14.10.
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 this vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. It is advised to update the Kernel to the recommended version.
Conclusion
The vulnerability in cpufreq: schedutil in the Kernel package can lead to memory leaks and potential exploitation. It is crucial to update the Linux Kernel to version v5.14.10 or later to mitigate this vulnerability. By applying the recommended update, the memory management issue will be resolved, ensuring the stability and security of the system. 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, but it has the potential to result in memory leaks and could potentially be exploited by attackers.
You can use the Vulert playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will provide real-time alerts for open-source vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the recommended update to mitigate any potential risks.
The details regarding remote exploitation have not been provided. However, it is always advisable to keep systems up to date to minimize the risk of remote attacks.
The specific prerequisites for exploiting this vulnerability have not been disclosed. However, updating the Linux Kernel to the recommended version will ensure that the vulnerability is addressed.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.