<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T23:49:17.679730+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-64278</id>
    <title>CVE-2026-64278 — i2c: imx-lpi2c: mark I2C adapter when hardware is powered down</title>
    <updated>2026-09-29T23:49:17.712982+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>i2c: imx-lpi2c: mark I2C adapter when hardware is powered down</p>
<p>On some i.MX platforms, certain I2C client drivers keep a periodic
workqueue which continues to trigger I2C transfers.</p>
<p>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</p>
<p>In this window, the I2C controller resources such as clock and pinctrl
may already be disabled or not yet restored.</p>
<p>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.</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64278"/>
  </entry>
</feed>
