CVE-2022-50494: thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-10-04 · updated 2026-06-17

Description

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 ]

Affected products

Linux kernel: from 3.9 before 4.9.331; from 4.10 before 4.14.296; from 4.15 before 4.19.262; from 4.20 before 5.4.220; from 5.5 before 5.10.150; from 5.11 before 5.15.75 — fixed in 4.14.296, 4.19.262, 4.9.331, 5.10.150, 5.15.75, 5.19.17

How to fix

Upgrade to a fixed version: Linux kernel 4.14.296, 4.19.262, 4.9.331, 5.10.150. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2022-50494 or the next vulnerability affects your stack