CVE-2026-64205
CVE CVE-2026-64205EUVD EUVD-2026-46013Published 2026-07-20T16:27:53.000ZLast changed 2026-08-03T09:32:39.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 6.3; 1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <ef5a347532932f58748dad485c15039f5168c377; 1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <10dd1a736d557e310a77117832874729a0175d57; 1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <bb5133a7d5f3fe5c387770e25f2e00e682ce11ed; 1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <2ef69871b313aa0f02182795f5e0f5aa455f203c; patch: 7.2-rc1; patch: 6.18.39; patch: 0; 1f760b87e54cf56a25ab68f8dc625e339f6e46d5 <00904687b9c5527d569d9a1ca72119823e735a61; patch: 7.1.4; patch: 6.6.148; patch: 6.12.101
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.