Answer in brief
CVE-2022-50494 records a Medium severity (CVSS 5.5) vulnerability in thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <3e799e815097febbcb81b472285be824f5d089f9 || >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <0f91f66c568b316b19cb042cf50584467b3bdff4 || >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <6904727db0eb62fb0c2dce1cf331c341d97ee4b7 || >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <5a646c38f648185ee2c62f2a19da3c6f04e27612 || >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <513943bf879d45005213e6f5cfb7d9e9943f589f || >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <5614908434451aafbf9b24cb5247cf1d21269f76 || >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <6e2a347b304224b2aeb1c0ea000d1cf8a02cc592 || >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <418fae0700e85a498062424f8656435c32cdb200 || >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <68b99e94a4a2db6ba9b31fe0485e057b9354a640 | 3e799e815097febbcb81b472285be824f5d089f9, 0f91f66c568b316b19cb042cf50584467b3bdff4, 6904727db0eb62fb0c2dce1cf331c341d97ee4b7, 5a646c38f648185ee2c62f2a19da3c6f04e27612, 513943bf879d45005213e6f5cfb7d9e9943f589f, 5614908434451aafbf9b24cb5247cf1d21269f76, 6e2a347b304224b2aeb1c0ea000d1cf8a02cc592, 418fae0700e85a498062424f8656435c32cdb200, 68b99e94a4a2db6ba9b31fe0485e057b9354a640 |
| Linux/Linuxgeneric | 3.9 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.