CVE-2026-64225

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index

cgx_speed_mbps has 13 elements but RESP_LINKSTAT_SPEED can yield values 0-15. If it returns a value >= 13, this causes an out-of-bounds array access. Add a bounds check and default to speed 0 if the index is out of range.

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
3%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 12, 2026

Advisory Details (8)

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

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/985b5e38ac4f4d5ff03c8bfd8484353b440a1579
generic

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94071141f00bc414e8f8f7f5db3b5143d535299f
generic

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93d3dc81098cd60fb74d434ba7985ddfd9de5acb
generic

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8201bf45cc7c1c1a09290c4db8ab1e19801f8fec
generic

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47a4cf2229be379cf88f92e32e1240337cd6273f
generic

octeontx2-af: CGX: add bounds check to cgx_speed_mbps index - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c3d26b4a62454945ba9ef3af3174d3e40e7afef

Vendor Advisories for CVE-2026-64225(1)

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

Patch Availability(3)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 41× in last 7d / 120× 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 131 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64225?
CVE-2026-64225 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: CGX: add bounds check to cgxspeedmbps index cgxspeedmbps has 13 elements but RESPLINKSTATSPEED can yield values 0-15. If it returns a value >= 13, this causes an out-of-bounds array access. Add a bounds check and…
When was CVE-2026-64225 disclosed?
CVE-2026-64225 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64225 actively exploited?
CVE-2026-64225 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64225?
CVE-2026-64225 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64225?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64225, 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-64225

Explore →

Is Your Infrastructure Affected by CVE-2026-64225?

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