{"schema_version":"1.9.0","id":"CVE-2026-64205","published":"2026-07-20T16:27:53.310Z","modified":"2026-08-18T03:31:00.644317991Z","related":["CGA-jjqw-rf9h-483r","openSUSE-SU-2026:11476-1"],"summary":"i2c: i801: fix hardware state machine corruption in error path","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: i801: fix hardware state machine corruption in error path\n\nA severe livelock and subsequent Hung Task panic were observed in the\ni2c-i801 driver during concurrent Fuzzing. The crash is caused by an\nunconditional hardware register cleanup in the error handling path of\ni801_access().\n\nWhen i801_check_pre() fails (e.g., returning -EBUSY because the SMBus\ncontroller is actively used by BIOS/ACPI), the kernel does not actually\nacquire the hardware ownership. However, the code jumps to the 'out'\nlabel and executes:\n\n    iowrite8(SMBHSTSTS_INUSE_STS | STATUS_FLAGS, SMBHSTSTS(priv));\n\nThis forcefully clears the INUSE_STS lock and resets the hardware status\nflags without owning the controller. Doing so interrupts ongoing BIOS/ACPI\ntransactions and totally corrupts the SMBus hardware state machine.\n\nConsequently, all subsequent i801_access() calls fail at the pre-check\nstage, triggering an endless stream of \"SMBus is busy, can't use it!\"\nerror logs. Over a slow serial console, this printk flood monopolizes\nthe CPU (Console Livelock), starving other processes trying to acquire\nthe mmap_lock down_read semaphore, ultimately triggering the hung task\nwatchdog.\n\nFix this by moving the 'out' label below the hardware register cleanup.\nIf i801_check_pre() fails, we safely bypass the iowrite8() and only\nrelease the software locks (pm_runtime and mutex), strictly adhering to\nthe rule of not releasing resources that were never acquired.","affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"1f760b87e54cf56a25ab68f8dc625e339f6e46d5"},{"fixed":"2ef69871b313aa0f02182795f5e0f5aa455f203c"},{"fixed":"ef5a347532932f58748dad485c15039f5168c377"},{"fixed":"bb5133a7d5f3fe5c387770e25f2e00e682ce11ed"},{"fixed":"00904687b9c5527d569d9a1ca72119823e735a61"},{"fixed":"10dd1a736d557e310a77117832874729a0175d57"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64205.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.3.0"},{"fixed":"6.6.148"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.101"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.39"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.4"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64205.json"}}],"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/00904687b9c5527d569d9a1ca72119823e735a61"},{"type":"WEB","url":"https://git.kernel.org/stable/c/10dd1a736d557e310a77117832874729a0175d57"},{"type":"WEB","url":"https://git.kernel.org/stable/c/2ef69871b313aa0f02182795f5e0f5aa455f203c"},{"type":"WEB","url":"https://git.kernel.org/stable/c/bb5133a7d5f3fe5c387770e25f2e00e682ce11ed"},{"type":"WEB","url":"https://git.kernel.org/stable/c/ef5a347532932f58748dad485c15039f5168c377"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64205.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64205"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64205.json"}}