<?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>Wed, 30 Sep 2026 04:38:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64278 — i2c: imx-lpi2c: mark I2C adapter when hardware is powered down</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64278</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-lpi2c: mark I2C adapter when hardware is powered down&lt;/p&gt;
&lt;p&gt;On some i.MX platforms, certain I2C client drivers keep a periodic
workqueue which continues to trigger I2C transfers.&lt;/p&gt;
&lt;p&gt;During system suspend/resume, there exists a time window between:
  - suspend_noirq and the system entering suspend
  - the system starting to resume and resume_noirq&lt;/p&gt;
&lt;p&gt;In this window, the I2C controller resources such as clock and pinctrl
may already be disabled or not yet restored.&lt;/p&gt;
&lt;p&gt;If a workqueue triggers an I2C transfer in this period, the driver
attempts to access I2C registers while the hardware resources are
unavailable, which may lead to system hang.&lt;/p&gt;
&lt;p&gt;Mark the I2C adapter as suspended during noirq suspend and block new
transfers until resume, ensuring that I2C transfers are only issued
when hardware resources are available.&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-lpi2c: mark I2C adapter when hardware is powered down&lt;/p&gt;
&lt;p&gt;On some i.MX platforms, certain I2C client drivers keep a periodic
workqueue which continues to trigger I2C transfers.&lt;/p&gt;
&lt;p&gt;During system suspend/resume, there exists a time window between:
  - suspend_noirq and the system entering suspend
  - the system starting to resume and resume_noirq&lt;/p&gt;
&lt;p&gt;In this window, the I2C controller resources such as clock and pinctrl
may already be disabled or not yet restored.&lt;/p&gt;
&lt;p&gt;If a workqueue triggers an I2C transfer in this period, the driver
attempts to access I2C registers while the hardware resources are
unavailable, which may lead to system hang.&lt;/p&gt;
&lt;p&gt;Mark the I2C adapter as suspended during noirq suspend and block new
transfers until resume, ensuring that I2C transfers are only issued
when hardware resources are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64278</guid>
    </item>
  </channel>
</rss>
