thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d6d71ee4a14ae602db343ec48c491851d7ec5267 · < 5614908434451aafbf9b24cb5247cf1d21269f76| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash
When CPU 0 is offline and intel_powerclamp is used to inject idle, it generates kernel BUG:
BUG: using smp_processor_id() in preemptible [00000000] code: bash/15687 caller is debug_smp_processor_id+0x17/0x20 CPU: 4 PID: 15687 Comm: bash Not tainted 5.19.0-rc7+ #57 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 check_preemption_disabled+0xdd/0xe0 debug_smp_processor_id+0x17/0x20 powerclamp_set_cur_state+0x7f/0xf9 [intel_powerclamp] ... ...
Here CPU 0 is the control CPU by default and changed to the current CPU, if CPU 0 offlined. This check has to be performed under cpus_read_lock(), hence the above warning.
Use get_cpu() instead of smp_processor_id() to avoid this BUG.
[ rjw: Subject edits ]
From the CVE record · Linux
The Linux kernel's intel_powerclamp component can trigger a kernel BUG when CPU 0 is offline and it injects idle. This occurs on the affected system; the input does not establish whether an attacker can trigger it, what privileges would be needed, or whether user interaction is required.
Operators running Linux kernels with intel_powerclamp should check their systems, particularly where CPU 0 can be offline; no affected version range is specified.