<?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 11:43:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64205 — i2c: i801: fix hardware state machine corruption in error path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64205</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: i801: fix hardware state machine corruption in error path&lt;/p&gt;
&lt;p&gt;A severe livelock and subsequent Hung Task panic were observed in the
i2c-i801 driver during concurrent Fuzzing. The crash is caused by an
unconditional hardware register cleanup in the error handling path of
i801_access().&lt;/p&gt;
&lt;p&gt;When i801_check_pre() fails (e.g., returning -EBUSY because the SMBus
controller is actively used by BIOS/ACPI), the kernel does not actually
acquire the hardware ownership. However, the code jumps to the &amp;#39;out&amp;#39;
label and executes:&lt;/p&gt;
&lt;p&gt;iowrite8(SMBHSTSTS_INUSE_STS | STATUS_FLAGS, SMBHSTSTS(priv));&lt;/p&gt;
&lt;p&gt;This forcefully clears the INUSE_STS lock and resets the hardware status
flags without owning the controller. Doing so interrupts ongoing BIOS/ACPI
transactions and totally corrupts the SMBus hardware state machine.&lt;/p&gt;
&lt;p&gt;Consequently, all subsequent i801_access() calls fail at the pre-check
stage, triggering an endless stream of &amp;#34;SMBus is busy, can&amp;#39;t use it!&amp;#34;
error logs. Over a slow serial console, this printk flood monopolizes
the CPU (Console Livelock), starving other processes trying to acquire
the mmap_lock down_read semaphore, ultimately triggering the hung task
watchdog.&lt;/p&gt;
&lt;p&gt;Fix this by moving the &amp;#39;out&amp;#39; label below the hardware register cleanup.
If i801_check_pre() fails, we safely bypass the iowrite8() and only
release the software locks (pm_runtime and mutex), strictly adhering to
the rule of not releasing resources that were ne…&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: i801: fix hardware state machine corruption in error path&lt;/p&gt;
&lt;p&gt;A severe livelock and subsequent Hung Task panic were observed in the
i2c-i801 driver during concurrent Fuzzing. The crash is caused by an
unconditional hardware register cleanup in the error handling path of
i801_access().&lt;/p&gt;
&lt;p&gt;When i801_check_pre() fails (e.g., returning -EBUSY because the SMBus
controller is actively used by BIOS/ACPI), the kernel does not actually
acquire the hardware ownership. However, the code jumps to the &amp;#39;out&amp;#39;
label and executes:&lt;/p&gt;
&lt;p&gt;iowrite8(SMBHSTSTS_INUSE_STS | STATUS_FLAGS, SMBHSTSTS(priv));&lt;/p&gt;
&lt;p&gt;This forcefully clears the INUSE_STS lock and resets the hardware status
flags without owning the controller. Doing so interrupts ongoing BIOS/ACPI
transactions and totally corrupts the SMBus hardware state machine.&lt;/p&gt;
&lt;p&gt;Consequently, all subsequent i801_access() calls fail at the pre-check
stage, triggering an endless stream of &amp;#34;SMBus is busy, can&amp;#39;t use it!&amp;#34;
error logs. Over a slow serial console, this printk flood monopolizes
the CPU (Console Livelock), starving other processes trying to acquire
the mmap_lock down_read semaphore, ultimately triggering the hung task
watchdog.&lt;/p&gt;
&lt;p&gt;Fix this by moving the &amp;#39;out&amp;#39; label below the hardware register cleanup.
If i801_check_pre() fails, we safely bypass the iowrite8() and only
release the software locks (pm_runtime and mutex), strictly adhering to
the rule of not releasing resources that were ne…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64205</guid>
    </item>
  </channel>
</rss>
