<?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 12:40:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-57984 — i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-57984</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;i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition&lt;/p&gt;
&lt;p&gt;In dw_i3c_common_probe, &amp;amp;master-&amp;gt;hj_work is bound with
dw_i3c_hj_work. And dw_i3c_master_irq_handler can call
dw_i3c_master_irq_handle_ibis function to start the work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call dw_i3c_common_remove to
make cleanup, it will free master-&amp;gt;base through i3c_master_unregister
while the work mentioned above will be used. The sequence of operations
that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| dw_i3c_hj_work
dw_i3c_common_remove                 |
i3c_master_unregister(&amp;amp;master-&amp;gt;base) |
device_unregister(&amp;amp;master-&amp;gt;dev)      |
device_release                       |
//free master-&amp;gt;base                  |
                                     | i3c_master_do_daa(&amp;amp;master-&amp;gt;base)
                                     | //use master-&amp;gt;base&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in dw_i3c_common_remove.&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;i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition&lt;/p&gt;
&lt;p&gt;In dw_i3c_common_probe, &amp;amp;master-&amp;gt;hj_work is bound with
dw_i3c_hj_work. And dw_i3c_master_irq_handler can call
dw_i3c_master_irq_handle_ibis function to start the work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call dw_i3c_common_remove to
make cleanup, it will free master-&amp;gt;base through i3c_master_unregister
while the work mentioned above will be used. The sequence of operations
that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| dw_i3c_hj_work
dw_i3c_common_remove                 |
i3c_master_unregister(&amp;amp;master-&amp;gt;base) |
device_unregister(&amp;amp;master-&amp;gt;dev)      |
device_release                       |
//free master-&amp;gt;base                  |
                                     | i3c_master_do_daa(&amp;amp;master-&amp;gt;base)
                                     | //use master-&amp;gt;base&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in dw_i3c_common_remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-57984</guid>
    </item>
  </channel>
</rss>
