thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4.9.331, Kernel 4.14.296, Kernel 4.19.262 and 14 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3.9 <4.9.331, >=4.10 <4.14.296, >=4.15 <4.19.262, >=4.20 <5.4.220, >=5.11 <5.15.75, >=5.16 <5.19.17, >=5.5 <5.10.150, >=6.0 <6.0.3, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <3e799e815097febbcb81b472285be824f5d089f9, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <418fae0700e85a498062424f8656435c32cdb200, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <513943bf879d45005213e6f5cfb7d9e9943f589f, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <5614908434451aafbf9b24cb5247cf1d21269f76, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <5a646c38f648185ee2c62f2a19da3c6f04e27612, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <68b99e94a4a2db6ba9b31fe0485e057b9354a640, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <6904727db0eb62fb0c2dce1cf331c341d97ee4b7, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <6e2a347b304224b2aeb1c0ea000d1cf8a02cc592, =3.9, >=d6d71ee4a14ae602db343ec48c491851d7ec5267 <0f91f66c568b316b19cb042cf50584467b3bdff4 | 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.15.75, 5.19.17, 5.10.150, 6.0.3, 3e799e815097febbcb81b472285be824f5d089f9, 418fae0700e85a498062424f8656435c32cdb200, 513943bf879d45005213e6f5cfb7d9e9943f589f, 5614908434451aafbf9b24cb5247cf1d21269f76, 5a646c38f648185ee2c62f2a19da3c6f04e27612, 68b99e94a4a2db6ba9b31fe0485e057b9354a640, 6904727db0eb62fb0c2dce1cf331c341d97ee4b7, 6e2a347b304224b2aeb1c0ea000d1cf8a02cc592, 0f91f66c568b316b19cb042cf50584467b3bdff4 |
| linux-kernel: Kernel | >=3.9.0 <4.9.331, >=4.10.0 <4.14.296, >=4.15.0 <4.19.262, >=4.20.0 <5.4.220, >=5.11.0 <5.15.75, >=5.16.0 <5.19.17, >=5.20.0 <6.0.3, >=5.5.0 <5.10.150 | 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.15.75, 5.19.17, 6.0.3, 5.10.150 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket