CVE-2022-50494

thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash

MEDIUM
5.5
CVSS Score
Published: October 4, 2025 at 03:43 PM UTC
Updated: June 17, 2026 at 05:23 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.9 ≤ v < 4.14.2963.9 ≤ v < 4.19.2623.9 ≤ v < 4.9.3313.9 ≤ v < 5.10.1503.9 ≤ v < 5.15.753.9 ≤ v < 5.19.173.9 ≤ v < 5.4.2203.9 ≤ v < 6.0.33.9 ≤ v < 6.14.10 ≤ v < 4.14.2964.15 ≤ v < 4.19.2624.20 ≤ v < 5.4.2205.11 ≤ v < 5.15.755.16 ≤ v < 5.19.175.5 ≤ v < 5.10.1506.0 ≤ v < 6.0.33.9d6d71ee4a14ae602db343ec48c491851d7ec5267
Vendor states this is fixed in 0f91f66c568b316b19cb042cf50584467b3bdff4 (fixed)
Vendor states this is fixed in 3e799e815097febbcb81b472285be824f5d089f9 (fixed)
Vendor states this is fixed in 418fae0700e85a498062424f8656435c32cdb200 (fixed)
Vendor states this is fixed in 513943bf879d45005213e6f5cfb7d9e9943f589f (fixed)
Vendor states this is fixed in 5614908434451aafbf9b24cb5247cf1d21269f76 (fixed)
Vendor states this is fixed in 5a646c38f648185ee2c62f2a19da3c6f04e27612 (fixed)
Vendor states this is fixed in 68b99e94a4a2db6ba9b31fe0485e057b9354a640 (fixed)
Vendor states this is fixed in 6904727db0eb62fb0c2dce1cf331c341d97ee4b7 (fixed)
Vendor states this is fixed in 6e2a347b304224b2aeb1c0ea000d1cf8a02cc592 (fixed)
Vendor states this is fixed in 3.9 (unaffected)
Vendor states this is fixed in 4.14.296 (unaffected)
Vendor states this is fixed in 4.19.262 (unaffected)
Vendor states this is fixed in 4.9.331 (unaffected)
Vendor states this is fixed in 5.10.150 (unaffected)
Vendor states this is fixed in 5.15.75 (unaffected)
Vendor states this is fixed in 5.19.17 (unaffected)
Vendor states this is fixed in 5.4.220 (unaffected)
Vendor states this is fixed in 6.0.3 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card