CVE-2026-64086

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer

adm1266_pmbus_block_xfer() sets up the read transaction with

.buf = data->read_buf, .len = ADM1266_PMBUS_BLOCK_MAX + 2,

but read_buf in struct adm1266_data is declared as

u8 read_buf[ADM1266_PMBUS_BLOCK_MAX + 1];

For a max-length block response (length byte = 255 + up to 1 PEC byte), the i2c controller is told to write 257 bytes into a 256-byte buffer, putting one byte past the end of read_buf. The same response also makes the subsequent PEC compare

if (crc != msgs[1].buf[msgs[1].buf[0] + 1])

read a byte beyond the array.

Bump the read_buf declaration to ADM1266_PMBUS_BLOCK_MAX + 2 so the buffer can hold the length byte, up to 255 payload bytes, and the PEC byte the i2c_msg length already accounts for.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/528a9f88e88502d0c2f2052a279415074cd83715
generic

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/487566cb1ccdf3756fdd7bf8d875e612ff3169bb
generic

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/472744f69d25a2d5111ad62f1d62579dce2c13c8
generic

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/397d3f523bfff2f4e3dacf9b1339bd76dc207f78
generic

hwmon: (pmbus/adm1266) include PEC byte in pmbus_block_xfer read buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2279c342d94eca225bf9f301c8806a05a1c81619

Vendor Advisories for CVE-2026-64086(1)

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

Patch Availability(16)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 30× in last 7d / 160× 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 213 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64086?
CVE-2026-64086 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) include PEC byte in pmbusblockxfer read buffer adm1266pmbusblock_xfer() sets up the read transaction with .buf = data->read_buf, .len = ADM1266PMBUSBLOCK_MAX + 2, but readbuf in struct adm1266data is declared…
When was CVE-2026-64086 disclosed?
CVE-2026-64086 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64086 actively exploited?
CVE-2026-64086 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 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64086?
CVE-2026-64086 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64086?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64086, 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-64086

Explore →

Is Your Infrastructure Affected by CVE-2026-64086?

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