In the Linux kernel, the following vulnerability has been resolved: cpufreq: schedutil: Use kobject release() method to free sugov_tunables The Linux kernel CVE team has assigned CVE-2021-47387 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052145-CVE-2021-47387-7c1e@gregkh/T
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2021-47387 is: CHECK Maybe valid. Check manually. with impact LOW (that is an approximation based on flags INIT WARNONLY ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.
Alex, any thoughts regarding the above?
In reply to comment #7: > Alex, any thoughts regarding the above? I agree to keep it Low. Looks like bug can happen only during initialization/exit of this kernel module. Also I read about "sugov" a little bit and it looks like this is specific module for RT: "In system where multiple CPUs shares the same frequency domain a small workload on a CPU can still be subject to frequency spikes, generated by the activation of the sugov's kthread. Since the sugov kthread is a special RT task, which goal is just that to activate a frequency transition, ..". And I cannot think of scenario how regular local user can use it (trigger this bug), so PR:H for CVSS.