<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T20:59:29.466638+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-36932</id>
    <title>CVE-2024-36932 — thermal/debugfs: Prevent use-after-free from occurring after cdev removal</title>
    <updated>2026-10-03T20:59:29.469082+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, linux_kernel</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>thermal/debugfs: Prevent use-after-free from occurring after cdev removal</p>
<p>Since thermal_debug_cdev_remove() does not run under cdev-&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.</p>
<p>If that happens, thermal_debug_cdev_state_update() will access memory
that has been freed already causing the kernel to crash.</p>
<p>Address this by using cdev-&gt;lock in thermal_debug_cdev_remove() around
the cdev-&gt;debugfs value check (in case the same cdev is removed at the
same time in two different threads) and its reset to NULL.</p>
<p>Cc :6.8+ &lt;stable@vger.kernel.org&gt; # 6.8+</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-36932"/>
  </entry>
</feed>
