CVE-2026-64205: i2c: i801: fix hardware state machine corruption in error path
Published Jul 20, 2026
·Updated
i2c: i801: fix hardware state machine corruption in error path
Affected Software
6 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.145.2-1<6.6.150.1-1
6.6.150.1-1
Linux Linux kernel>=6.3<6.6.148
Linux Linux kernel>=6.7<6.12.101
Linux Linux kernel>=6.13<6.18.39
Linux Linux kernel>=6.19<7.1.4
Remediation
Event History
Jul 20, 2026
CVE Published
via MITRE·04:27 PM
Data Sourced
via MITRE·04:27 PM
Description
Data Sourced
via NVD·05:18 PM
RemedyDescriptionSeverityAffected Software
Jul 22, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-64205?
The severity of CVE-2026-64205 is rated at 34, indicating a significant security concern.
2
How do I fix CVE-2026-64205?
To fix CVE-2026-64205, update your Linux kernel to the latest version that includes the patch for this vulnerability.
3
What systems are affected by CVE-2026-64205?
CVE-2026-64205 affects systems running vulnerable versions of the Linux kernel that utilize the i2c-i801 driver.
4
What are the consequences of CVE-2026-64205?
The consequences of CVE-2026-64205 include the risk of livelocks and Hung Task panics during concurrent operations, potentially leading to system instability.
5
Is there a workaround for CVE-2026-64205 if I cannot update my kernel?
While the best practice is to update the kernel, disabling the i2c-i801 driver may serve as a temporary workaround for CVE-2026-64205.