CVE-2026-64205

published 20 Jul 2026 · updated 15 Nov 2026

i2c: i801: fix hardware state machine corruption in error path

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.18.39, Kernel 7.1.4, Kernel 6.6.148 and 6 more.

In the Linux kernel, the following vulnerability has been resolved: i2c: i801: fix hardware state machine corruption in error path 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(). 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 'out' label and executes: iowrite8(SMBHSTSTS_INUSE_STS | STATUS_FLAGS, SMBHSTSTS(priv)); 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. Consequently, all subsequent i801_access() calls fail at the pre-check stage, triggering an endless stream of "SMBus is busy, can't use it!" 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. Fix this by moving the 'out' 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 never acquired.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=6.13 <6.18.39, >=6.19 <7.1.4, >=6.3 <6.6.148, >=6.7 <6.12.101, >=1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <10dd1a736d557e310a77117832874729a0175d57, >=1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <2ef69871b313aa0f02182795f5e0f5aa455f203c, >=1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <bb5133a7d5f3fe5c387770e25f2e00e682ce11ed, >=1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <ef5a347532932f58748dad485c15039f5168c377, =6.3, >=1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <00904687b9c5527d569d9a1ca72119823e735a616.18.39, 7.1.4, 6.6.148, 6.12.101, 10dd1a736d557e310a77117832874729a0175d57, 2ef69871b313aa0f02182795f5e0f5aa455f203c, bb5133a7d5f3fe5c387770e25f2e00e682ce11ed, ef5a347532932f58748dad485c15039f5168c377, 00904687b9c5527d569d9a1ca72119823e735a61
linux-kernel: Kernel>=6.13.0 <6.18.39, >=6.19.0 <7.1.4, >=6.3.0 <6.6.148, >=6.7.0 <6.12.1016.18.39, 7.1.4, 6.6.148, 6.12.101

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64205 severity on Zeptric[![CVE-2026-64205](https://zeptric.io/badge/cve/CVE-2026-64205.svg)](https://zeptric.io/cve/CVE-2026-64205)