thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash
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: 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 ]
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.296, 4.19.262, 4.9.331, 5.10.150, 5.15.75, 5.19.17, 5.4.220, 6.0.3
- CVEs
- CVE-2022-50494
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:05 UTC · Revision 1
Source evidence
thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash
core-osv · Original sourcePublished 4 Oct 2025, 15:43 UTC
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: 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 ]
osv:CVE-2022-50494
Kernel
Fixed versions: 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3
Complete source record
{
"id": "efa8f29084fce6e8cdad64080b4b39a3681679187edba2768f06ffe88dc6d838",
"url": "https://osv.dev/vulnerability/CVE-2022-50494",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash",
"summary": "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: 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 ]",
"evidence": "osv:CVE-2022-50494",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.9.331",
"evidence": "/affected/1/ranges"
},
{
"value": "4.14.296",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.262",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.220",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.150",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.75",
"evidence": "/affected/1/ranges"
},
{
"value": "5.19.17",
"evidence": "/affected/1/ranges"
},
{
"value": "6.0.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-50494",
"aliases": [
"CVE-2022-50494"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d6d71ee4a14ae602db343ec48c491851d7ec5267"
},
{
"fixed": "3e799e815097febbcb81b472285be824f5d089f9"
},
{
"fixed": "0f91f66c568b316b19cb042cf50584467b3bdff4"
},
{
"fixed": "6904727db0eb62fb0c2dce1cf331c341d97ee4b7"
},
{
"fixed": "5a646c38f648185ee2c62f2a19da3c6f04e27612"
},
{
"fixed": "513943bf879d45005213e6f5cfb7d9e9943f589f"
},
{
"fixed": "5614908434451aafbf9b24cb5247cf1d21269f76"
},
{
"fixed": "6e2a347b304224b2aeb1c0ea000d1cf8a02cc592"
},
{
"fixed": "418fae0700e85a498062424f8656435c32cdb200"
},
{
"fixed": "68b99e94a4a2db6ba9b31fe0485e057b9354a640"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50494.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.9.0"
},
{
"fixed": "4.9.331"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.10.0"
},
{
"fixed": "4.14.296"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.262"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.220"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.150"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.75"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.19.17"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.20.0"
},
{
"fixed": "6.0.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50494.json"
}
}
],
"modified": "2026-10-28T02:30:22.876845508Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0f91f66c568b316b19cb042cf50584467b3bdff4",
"https://git.kernel.org/stable/c/3e799e815097febbcb81b472285be824f5d089f9",
"https://git.kernel.org/stable/c/418fae0700e85a498062424f8656435c32cdb200",
"https://git.kernel.org/stable/c/513943bf879d45005213e6f5cfb7d9e9943f589f",
"https://git.kernel.org/stable/c/5614908434451aafbf9b24cb5247cf1d21269f76",
"https://git.kernel.org/stable/c/5a646c38f648185ee2c62f2a19da3c6f04e27612",
"https://git.kernel.org/stable/c/68b99e94a4a2db6ba9b31fe0485e057b9354a640",
"https://git.kernel.org/stable/c/6904727db0eb62fb0c2dce1cf331c341d97ee4b7",
"https://git.kernel.org/stable/c/6e2a347b304224b2aeb1c0ea000d1cf8a02cc592",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50494.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-50494",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50494.json"
}
},
"related_cves": [
{
"value": "CVE-2022-50494",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 488945,
"published_at": "2025-10-04T15:43:46.562+00:00"
}