CVE-2026-64205

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-20. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 20, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

i2c: i801: fix hardware state machine corruption in error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef5a347532932f58748dad485c15039f5168c377
generic

i2c: i801: fix hardware state machine corruption in error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb5133a7d5f3fe5c387770e25f2e00e682ce11ed
generic

i2c: i801: fix hardware state machine corruption in error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ef69871b313aa0f02182795f5e0f5aa455f203c
generic

i2c: i801: fix hardware state machine corruption in error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10dd1a736d557e310a77117832874729a0175d57
generic

i2c: i801: fix hardware state machine corruption in error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00904687b9c5527d569d9a1ca72119823e735a61

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.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-11ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-11ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u16.12.101-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)6.12.101-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 87× 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 402 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64205?
CVE-2026-64205 is a medium 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, with the most recent update on August 17, 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 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-64205?
CVE-2026-64205 has a CVSS v3 base score of 5.5 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.