CVE-2024-40997 cpufreq: amd-pstate: fix memory leak on CPU EPP exit

In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: fix memory leak on CPU EPP exit The cpudata memory from kzalloc in amdpstateeppcpuinit is not freed in the analogous exit function, so fix that. rjw: Subject and changelog edits...

cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value

...

SUSE CVE-2024-38573

In the Linux kernel, the following vulnerability has been resolved: cppccpufreq: Fix possible null pointer dereference cppccpufreqgetrate and hisicppccpufreqgetrate can be called from different places with various parameters. So cpufreqcpuget can return null as 'policy' in some circumstances. Fix...

SUSE CVE-2024-38615

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

CVE-2024-38615

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

CVE-2024-38615

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

DEBIAN-CVE-2024-38615

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

DEBIAN-CVE-2024-38573

In the Linux kernel, the following vulnerability has been resolved: cppccpufreq: Fix possible null pointer dereference cppccpufreqgetrate and hisicppccpufreqgetrate can be called from different places with various parameters. So cpufreqcpuget can return null as 'policy' in some circumstances. Fix...

CVE-2024-38615

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

CVE-2024-38615 cpufreq: exit() callback is optional

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

CVE-2024-38615

CVE-2024-38615 : A Linux kernel cpufreq vulnerability was resolved. The issue centers on the cpufreq exit() callback which is now optional; code must not call exit() without validating the pointer first, and freq_table must be cleared even if the exit() callback is absent. The connected Astra Lin...

CVE-2024-38615 cpufreq: exit() callback is optional

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

CVE-2024-38615 cpufreq: exit() callback is optional

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

CVE-2024-38615

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit callback is optional The exit callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freqtable pointer even if the exit callback isn't present...

SUSE CVE-2021-47387

In the Linux kernel, the following vulnerability has been resolved: cpufreq: schedutil: Use kobject release method to free sugovtunables The struct sugovtunables is protected by the kobject, so we can't free it directly. Otherwise we would get a call trace like this: ODEBUG: free active active...

CVE-2021-47387

In the Linux kernel, the following vulnerability has been resolved: cpufreq: schedutil: Use kobject release method to free sugovtunables The struct sugovtunables is protected by the kobject, so we can't free it directly. Otherwise we would get a call trace like this: ODEBUG: free active active...

CVE-2021-47313

In the Linux kernel, the following vulnerability has been resolved: cpufreq: CPPC: Fix potential memleak in cppccpufreqcpuinit It's a classic example of memleak, we allocate something, we fail and never free the resources. Make sure we free all resources on policy -init failures...

UBUNTU-CVE-2021-47387

In the Linux kernel, the following vulnerability has been resolved: cpufreq: schedutil: Use kobject release method to free sugovtunables The struct sugovtunables is protected by the kobject, so we can't free it directly. Otherwise we would get a call trace like this: ODEBUG: free active active...

CVE-2021-47387

In the Linux kernel, the following vulnerability has been resolved: cpufreq: schedutil: Use kobject release method to free sugovtunables The struct sugovtunables is protected by the kobject, so we can't free it directly. Otherwise we would get a call trace like this: ODEBUG: free active active...

CVE-2021-47387

CVE-2021-47387 is a Linux kernel vulnerability in the cpufreq: schedutil governor related to freeing sugov_tunables. The original sugov_tunables_free() was split: sugov_clear_global_tunables() clears the global_tunables, and a new sugov_tunables_free() is used as kobj_type::release to safely free...