<?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://cve.radiocsirt.org</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>Mon, 05 Oct 2026 03:05:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80953 — i3c: master: adi: initialize the lock before enabling interrupts</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-80953</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: adi: initialize the lock before enabling interrupts&lt;/p&gt;
&lt;p&gt;adi_i3c_master_probe() requests the IRQ and unmasks REG_IRQ_PENDING_CMDR
before the controller&amp;#39;s IBI state, transfer queue list and transfer
queue lock are initialized.  A pending CMDR interrupt can therefore run
adi_i3c_master_irq() and take master-&amp;gt;xferqueue.lock before the dynamic
lock has been initialized.&lt;/p&gt;
&lt;p&gt;This issue was found by our static analysis tool and then manually
reviewed against the current tree.&lt;/p&gt;
&lt;p&gt;The grounded PoC kept the probe ordering and the IRQ path
adi_i3c_master_probe() -&amp;gt; adi_i3c_master_irq() -&amp;gt; xferqueue.lock, with a
pending CMDR interrupt arriving after REG_IRQ_PENDING_CMDR is unmasked.
Lockdep reported:&lt;/p&gt;
&lt;p&gt;INFO: trying to register non-static key.
  you didn&amp;#39;t initialize this object before use?
  lock_acquire+0xbb/0x290
  _raw_spin_lock_irqsave+0x36/0x60
  adi_i3c_master_irq+0x32/0x56 [vuln_msv]
  adi_i3c_master_probe+0x5a/0xf47 [vuln_msv]&lt;/p&gt;
&lt;p&gt;Initialize the transfer queue and IBI state before requesting and
unmasking the IRQ.&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: adi: initialize the lock before enabling interrupts&lt;/p&gt;
&lt;p&gt;adi_i3c_master_probe() requests the IRQ and unmasks REG_IRQ_PENDING_CMDR
before the controller&amp;#39;s IBI state, transfer queue list and transfer
queue lock are initialized.  A pending CMDR interrupt can therefore run
adi_i3c_master_irq() and take master-&amp;gt;xferqueue.lock before the dynamic
lock has been initialized.&lt;/p&gt;
&lt;p&gt;This issue was found by our static analysis tool and then manually
reviewed against the current tree.&lt;/p&gt;
&lt;p&gt;The grounded PoC kept the probe ordering and the IRQ path
adi_i3c_master_probe() -&amp;gt; adi_i3c_master_irq() -&amp;gt; xferqueue.lock, with a
pending CMDR interrupt arriving after REG_IRQ_PENDING_CMDR is unmasked.
Lockdep reported:&lt;/p&gt;
&lt;p&gt;INFO: trying to register non-static key.
  you didn&amp;#39;t initialize this object before use?
  lock_acquire+0xbb/0x290
  _raw_spin_lock_irqsave+0x36/0x60
  adi_i3c_master_irq+0x32/0x56 [vuln_msv]
  adi_i3c_master_probe+0x5a/0xf47 [vuln_msv]&lt;/p&gt;
&lt;p&gt;Initialize the transfer queue and IBI state before requesting and
unmasking the IRQ.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-80953</guid>
    </item>
  </channel>
</rss>
