<?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>Thu, 01 Oct 2026 05:16:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-49976 — tracing/timerlat: Drop interface_lock in stop_kthread()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-49976</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;tracing/timerlat: Drop interface_lock in stop_kthread()&lt;/p&gt;
&lt;p&gt;stop_kthread() is the offline callback for &amp;#34;trace/osnoise:online&amp;#34;, since
commit 5bfbcd1ee57b (&amp;#34;tracing/timerlat: Add interface_lock around clearing
of kthread in stop_kthread()&amp;#34;), the following ABBA deadlock scenario is
introduced:&lt;/p&gt;
&lt;p&gt;T1                            | T2 [BP]               | T3 [AP]
osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()
                              |   _cpu_down()         |   osnoise_cpu_die()
  mutex_lock(&amp;amp;interface_lock) |                       |     stop_kthread()
                              |     cpus_write_lock() |       mutex_lock(&amp;amp;interface_lock)
  cpus_read_lock()            |     cpuhp_kick_ap()   |&lt;/p&gt;
&lt;p&gt;As the interface_lock here in just for protecting the &amp;#34;kthread&amp;#34; field of
the osn_var, use xchg() instead to fix this issue. Also use
for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take
cpu_read_lock() again.&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;tracing/timerlat: Drop interface_lock in stop_kthread()&lt;/p&gt;
&lt;p&gt;stop_kthread() is the offline callback for &amp;#34;trace/osnoise:online&amp;#34;, since
commit 5bfbcd1ee57b (&amp;#34;tracing/timerlat: Add interface_lock around clearing
of kthread in stop_kthread()&amp;#34;), the following ABBA deadlock scenario is
introduced:&lt;/p&gt;
&lt;p&gt;T1                            | T2 [BP]               | T3 [AP]
osnoise_hotplug_workfn()      | work_for_cpu_fn()     | cpuhp_thread_fun()
                              |   _cpu_down()         |   osnoise_cpu_die()
  mutex_lock(&amp;amp;interface_lock) |                       |     stop_kthread()
                              |     cpus_write_lock() |       mutex_lock(&amp;amp;interface_lock)
  cpus_read_lock()            |     cpuhp_kick_ap()   |&lt;/p&gt;
&lt;p&gt;As the interface_lock here in just for protecting the &amp;#34;kthread&amp;#34; field of
the osn_var, use xchg() instead to fix this issue. Also use
for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take
cpu_read_lock() again.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-49976</guid>
    </item>
  </channel>
</rss>
