<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 19:58:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50494 — thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50494</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash&lt;/p&gt;
&lt;p&gt;When CPU 0 is offline and intel_powerclamp is used to inject
idle, it generates kernel BUG:&lt;/p&gt;
&lt;p&gt;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:
&amp;lt;TASK&amp;gt;
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]
...
...&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Use get_cpu() instead of smp_processor_id() to avoid this BUG.&lt;/p&gt;
&lt;p&gt;[ rjw: Subject edits ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash&lt;/p&gt;
&lt;p&gt;When CPU 0 is offline and intel_powerclamp is used to inject
idle, it generates kernel BUG:&lt;/p&gt;
&lt;p&gt;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:
&amp;lt;TASK&amp;gt;
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]
...
...&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Use get_cpu() instead of smp_processor_id() to avoid this BUG.&lt;/p&gt;
&lt;p&gt;[ rjw: Subject edits ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50494</guid>
    </item>
  </channel>
</rss>
