CVE-2026-64205

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
EG Score
0.0(none)
EG Risk
0
EG Risk 0/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses intrinsic severity with real-world exploitation and automatability, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. It is distinct from the 0–10 EG Score, which measures severity.

EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 20, 2026

Vendor Advisories for CVE-2026-64205(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 283× in last 7d / 283× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 283 total refreshes for this CVE.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 10:47 UTCEG score recompute
  4. 2026-07-26 10:47 UTCGHSA enrichment
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:22 UTCEG score recompute
  12. 2026-07-22 23:35 UTCEG score recompute
  13. 2026-07-22 23:35 UTCGHSA enrichment
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:25 UTCEPSS rescore
  17. 2026-07-21 15:25 UTCEPSS rescore
  18. 2026-07-21 07:55 UTCGHSA enrichment
  19. 2026-07-21 07:45 UTCGHSA enrichment
  20. 2026-07-21 04:14 UTCGHSA enrichment
  21. 2026-07-21 04:06 UTCGHSA enrichment
  22. 2026-07-21 03:38 UTCGHSA enrichment
  23. 2026-07-21 01:25 UTCGHSA enrichment
  24. 2026-07-20 23:50 UTCGHSA enrichment
  25. 2026-07-20 23:45 UTCGHSA enrichment
Show 75 more
  1. 2026-07-20 23:43 UTCGHSA enrichment
  2. 2026-07-20 23:42 UTCGHSA enrichment
  3. 2026-07-20 23:42 UTCGHSA enrichment
  4. 2026-07-20 23:41 UTCGHSA enrichment
  5. 2026-07-20 23:41 UTCGHSA enrichment
  6. 2026-07-20 23:39 UTCGHSA enrichment
  7. 2026-07-20 23:39 UTCGHSA enrichment
  8. 2026-07-20 23:39 UTCGHSA enrichment
  9. 2026-07-20 23:37 UTCGHSA enrichment
  10. 2026-07-20 23:36 UTCGHSA enrichment
  11. 2026-07-20 23:36 UTCGHSA enrichment
  12. 2026-07-20 23:35 UTCGHSA enrichment
  13. 2026-07-20 23:35 UTCGHSA enrichment
  14. 2026-07-20 23:34 UTCGHSA enrichment
  15. 2026-07-20 23:34 UTCGHSA enrichment
  16. 2026-07-20 23:33 UTCGHSA enrichment
  17. 2026-07-20 23:33 UTCGHSA enrichment
  18. 2026-07-20 23:32 UTCGHSA enrichment
  19. 2026-07-20 23:29 UTCGHSA enrichment
  20. 2026-07-20 23:28 UTCGHSA enrichment
  21. 2026-07-20 23:28 UTCGHSA enrichment
  22. 2026-07-20 23:28 UTCGHSA enrichment
  23. 2026-07-20 23:22 UTCGHSA enrichment
  24. 2026-07-20 23:21 UTCGHSA enrichment
  25. 2026-07-20 23:20 UTCGHSA enrichment
  26. 2026-07-20 23:19 UTCGHSA enrichment
  27. 2026-07-20 23:19 UTCGHSA enrichment
  28. 2026-07-20 23:18 UTCGHSA enrichment
  29. 2026-07-20 23:17 UTCGHSA enrichment
  30. 2026-07-20 23:16 UTCGHSA enrichment
  31. 2026-07-20 23:16 UTCGHSA enrichment
  32. 2026-07-20 23:15 UTCGHSA enrichment
  33. 2026-07-20 23:15 UTCGHSA enrichment
  34. 2026-07-20 23:14 UTCGHSA enrichment
  35. 2026-07-20 23:14 UTCGHSA enrichment
  36. 2026-07-20 23:13 UTCGHSA enrichment
  37. 2026-07-20 23:12 UTCGHSA enrichment
  38. 2026-07-20 23:11 UTCGHSA enrichment
  39. 2026-07-20 23:11 UTCGHSA enrichment
  40. 2026-07-20 23:10 UTCGHSA enrichment
  41. 2026-07-20 23:10 UTCGHSA enrichment
  42. 2026-07-20 23:09 UTCGHSA enrichment
  43. 2026-07-20 23:08 UTCGHSA enrichment
  44. 2026-07-20 23:07 UTCGHSA enrichment
  45. 2026-07-20 23:06 UTCGHSA enrichment
  46. 2026-07-20 23:06 UTCGHSA enrichment
  47. 2026-07-20 23:04 UTCGHSA enrichment
  48. 2026-07-20 23:02 UTCGHSA enrichment
  49. 2026-07-20 23:01 UTCGHSA enrichment
  50. 2026-07-20 23:00 UTCGHSA enrichment
  51. 2026-07-20 22:59 UTCGHSA enrichment
  52. 2026-07-20 22:59 UTCGHSA enrichment
  53. 2026-07-20 22:58 UTCGHSA enrichment
  54. 2026-07-20 22:58 UTCGHSA enrichment
  55. 2026-07-20 22:57 UTCGHSA enrichment
  56. 2026-07-20 22:57 UTCGHSA enrichment
  57. 2026-07-20 22:56 UTCGHSA enrichment
  58. 2026-07-20 22:56 UTCGHSA enrichment
  59. 2026-07-20 22:55 UTCGHSA enrichment
  60. 2026-07-20 22:55 UTCGHSA enrichment
  61. 2026-07-20 22:54 UTCGHSA enrichment
  62. 2026-07-20 22:54 UTCGHSA enrichment
  63. 2026-07-20 22:53 UTCGHSA enrichment
  64. 2026-07-20 22:53 UTCGHSA enrichment
  65. 2026-07-20 22:52 UTCGHSA enrichment
  66. 2026-07-20 22:52 UTCGHSA enrichment
  67. 2026-07-20 22:48 UTCGHSA enrichment
  68. 2026-07-20 22:48 UTCGHSA enrichment
  69. 2026-07-20 22:46 UTCGHSA enrichment
  70. 2026-07-20 22:46 UTCGHSA enrichment
  71. 2026-07-20 22:44 UTCGHSA enrichment
  72. 2026-07-20 22:43 UTCGHSA enrichment
  73. 2026-07-20 22:31 UTCGHSA enrichment
  74. 2026-07-20 22:30 UTCGHSA enrichment
  75. 2026-07-20 22:30 UTCGHSA enrichment

Frequently asked(4)

What is CVE-2026-64205?
CVE-2026-64205 is a publicly disclosed vulnerability published on July 20, 2026. 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…
When was CVE-2026-64205 disclosed?
CVE-2026-64205 was first published in the National Vulnerability Database on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64205 actively exploited?
CVE-2026-64205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
How do I remediate CVE-2026-64205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64205, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-64205

Explore →

Is Your Infrastructure Affected by CVE-2026-64205?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.