cpufreq/longhaul: handle NULL policy in longhaul_exit
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 · < 64adabb6d9d51b7e7c02fe733346a2c4dd738488| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
cpufreq/longhaul: handle NULL policy in longhaul_exit
longhaul_exit() was calling cpufreq_cpu_get(0) without checking for a NULL policy pointer. On some systems, this could lead to a NULL dereference and a kernel warning or panic.
This patch adds a check using unlikely() and returns early if the policy is NULL.
Bugzilla: #219962
From the CVE record · Linux
The Linux kernel's longhaul_exit() can dereference a NULL policy pointer on some systems, causing a kernel warning or panic. The input does not establish an attacker path or specify network access, authentication, or user interaction requirements.
Engineers running Linux systems that use the cpufreq/longhaul component should check their kernel; affected versions are not specified.