<?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>Fri, 02 Oct 2026 13:13:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-23147 — i3c: Add NULL pointer check in i3c_master_queue_ibi()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-23147</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: Add NULL pointer check in i3c_master_queue_ibi()&lt;/p&gt;
&lt;p&gt;The I3C master driver may receive an IBI from a target device that has not
been probed yet. In such cases, the master calls `i3c_master_queue_ibi()`
to queue an IBI work task, leading to &amp;#34;Unable to handle kernel read from
unreadable memory&amp;#34; and resulting in a kernel panic.&lt;/p&gt;
&lt;p&gt;Typical IBI handling flow:
1. The I3C master scans target devices and probes their respective drivers.
2. The target device driver calls `i3c_device_request_ibi()` to enable IBI
   and assigns `dev-&amp;gt;ibi = ibi`.
3. The I3C master receives an IBI from the target device and calls
   `i3c_master_queue_ibi()` to queue the target device driver’s IBI
   handler task.&lt;/p&gt;
&lt;p&gt;However, since target device events are asynchronous to the I3C probe
sequence, step 3 may occur before step 2, causing `dev-&amp;gt;ibi` to be `NULL`,
leading to a kernel panic.&lt;/p&gt;
&lt;p&gt;Add a NULL pointer check in `i3c_master_queue_ibi()` to prevent accessing
an uninitialized `dev-&amp;gt;ibi`, ensuring stability.&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: Add NULL pointer check in i3c_master_queue_ibi()&lt;/p&gt;
&lt;p&gt;The I3C master driver may receive an IBI from a target device that has not
been probed yet. In such cases, the master calls `i3c_master_queue_ibi()`
to queue an IBI work task, leading to &amp;#34;Unable to handle kernel read from
unreadable memory&amp;#34; and resulting in a kernel panic.&lt;/p&gt;
&lt;p&gt;Typical IBI handling flow:
1. The I3C master scans target devices and probes their respective drivers.
2. The target device driver calls `i3c_device_request_ibi()` to enable IBI
   and assigns `dev-&amp;gt;ibi = ibi`.
3. The I3C master receives an IBI from the target device and calls
   `i3c_master_queue_ibi()` to queue the target device driver’s IBI
   handler task.&lt;/p&gt;
&lt;p&gt;However, since target device events are asynchronous to the I3C probe
sequence, step 3 may occur before step 2, causing `dev-&amp;gt;ibi` to be `NULL`,
leading to a kernel panic.&lt;/p&gt;
&lt;p&gt;Add a NULL pointer check in `i3c_master_queue_ibi()` to prevent accessing
an uninitialized `dev-&amp;gt;ibi`, ensuring stability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-23147</guid>
    </item>
  </channel>
</rss>
