<?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 16:43:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80678 — i2c: imx: Fix slave registration race and error handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80678</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;i2c: imx: Fix slave registration race and error handling&lt;/p&gt;
&lt;p&gt;In i2c_imx_reg_slave(), the slave pointer was assigned before
pm_runtime_resume_and_get().  If pm_runtime_resume_and_get() failed,
the error path returned without clearing i2c_imx-&amp;gt;slave, leaving it
non-NULL and causing all subsequent registration attempts to fail
with -EBUSY.&lt;/p&gt;
&lt;p&gt;Additionally, because this driver uses a shared IRQ, the interrupt
handler i2c_imx_isr() can execute concurrently and, after acquiring
slave_lock, dereference i2c_imx-&amp;gt;slave.  The previous fix attempt
added a lockless i2c_imx-&amp;gt;slave = NULL on the error path, but that
could race with the ISR under the lock and still cause a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Fix both issues by deferring the assignment of i2c_imx-&amp;gt;slave and
i2c_imx-&amp;gt;last_slave_event to after a successful resume, and by
performing the assignment inside the slave_lock critical section.
This guarantees that the slave pointer is never left stale on the
error path and is always valid when observed by the interrupt handler.&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;i2c: imx: Fix slave registration race and error handling&lt;/p&gt;
&lt;p&gt;In i2c_imx_reg_slave(), the slave pointer was assigned before
pm_runtime_resume_and_get().  If pm_runtime_resume_and_get() failed,
the error path returned without clearing i2c_imx-&amp;gt;slave, leaving it
non-NULL and causing all subsequent registration attempts to fail
with -EBUSY.&lt;/p&gt;
&lt;p&gt;Additionally, because this driver uses a shared IRQ, the interrupt
handler i2c_imx_isr() can execute concurrently and, after acquiring
slave_lock, dereference i2c_imx-&amp;gt;slave.  The previous fix attempt
added a lockless i2c_imx-&amp;gt;slave = NULL on the error path, but that
could race with the ISR under the lock and still cause a NULL pointer
dereference.&lt;/p&gt;
&lt;p&gt;Fix both issues by deferring the assignment of i2c_imx-&amp;gt;slave and
i2c_imx-&amp;gt;last_slave_event to after a successful resume, and by
performing the assignment inside the slave_lock critical section.
This guarantees that the slave pointer is never left stale on the
error path and is always valid when observed by the interrupt handler.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80678</guid>
    </item>
  </channel>
</rss>
