<?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>Tue, 29 Sep 2026 01:28:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-49874 — i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-49874</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: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition&lt;/p&gt;
&lt;p&gt;In the svc_i3c_master_probe function, &amp;amp;master-&amp;gt;hj_work is bound with
svc_i3c_master_hj_work, &amp;amp;master-&amp;gt;ibi_work is bound with
svc_i3c_master_ibi_work. And svc_i3c_master_ibi_work  can start the
hj_work, svc_i3c_master_irq_handler can start the ibi_work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call svc_i3c_master_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;| svc_i3c_master_hj_work
svc_i3c_master_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 svc_i3c_master_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: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition&lt;/p&gt;
&lt;p&gt;In the svc_i3c_master_probe function, &amp;amp;master-&amp;gt;hj_work is bound with
svc_i3c_master_hj_work, &amp;amp;master-&amp;gt;ibi_work is bound with
svc_i3c_master_ibi_work. And svc_i3c_master_ibi_work  can start the
hj_work, svc_i3c_master_irq_handler can start the ibi_work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call svc_i3c_master_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;| svc_i3c_master_hj_work
svc_i3c_master_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 svc_i3c_master_remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-49874</guid>
    </item>
  </channel>
</rss>
