<?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>Sat, 03 Oct 2026 20:59:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36932 — thermal/debugfs: Prevent use-after-free from occurring after cdev removal</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-36932</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;thermal/debugfs: Prevent use-after-free from occurring after cdev removal&lt;/p&gt;
&lt;p&gt;Since thermal_debug_cdev_remove() does not run under cdev-&amp;gt;lock, it can
run in parallel with thermal_debug_cdev_state_update() and it may free
the struct thermal_debugfs object used by the latter after it has been
checked against NULL.&lt;/p&gt;
&lt;p&gt;If that happens, thermal_debug_cdev_state_update() will access memory
that has been freed already causing the kernel to crash.&lt;/p&gt;
&lt;p&gt;Address this by using cdev-&amp;gt;lock in thermal_debug_cdev_remove() around
the cdev-&amp;gt;debugfs value check (in case the same cdev is removed at the
same time in two different threads) and its reset to NULL.&lt;/p&gt;
&lt;p&gt;Cc :6.8+ &amp;lt;stable@vger.kernel.org&amp;gt; # 6.8+&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;thermal/debugfs: Prevent use-after-free from occurring after cdev removal&lt;/p&gt;
&lt;p&gt;Since thermal_debug_cdev_remove() does not run under cdev-&amp;gt;lock, it can
run in parallel with thermal_debug_cdev_state_update() and it may free
the struct thermal_debugfs object used by the latter after it has been
checked against NULL.&lt;/p&gt;
&lt;p&gt;If that happens, thermal_debug_cdev_state_update() will access memory
that has been freed already causing the kernel to crash.&lt;/p&gt;
&lt;p&gt;Address this by using cdev-&amp;gt;lock in thermal_debug_cdev_remove() around
the cdev-&amp;gt;debugfs value check (in case the same cdev is removed at the
same time in two different threads) and its reset to NULL.&lt;/p&gt;
&lt;p&gt;Cc :6.8+ &amp;lt;stable@vger.kernel.org&amp;gt; # 6.8+&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-36932</guid>
    </item>
  </channel>
</rss>
