CVE-2026-64222

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. A secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

octeontx2-pf: avoid double free of pool->stack on AQ init failure

otx2_pool_aq_init() frees pool->stack when mailbox sync or retry allocation fails, but leaves the pointer unchanged. Later, otx2_sq_aura_pool_init() unwinds the partial setup through otx2_aura_pool_free(), which frees pool->stack again. The CN20K-specific cn20k_pool_aq_init() implementation has the same bug in its corresponding error path.

Set pool->stack to NULL immediately after the local free so the shared cleanup path does not free the same stack again while cleaning up partially initialized pool state.

The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1-rc3.

Runtime validation was not performed because reproducing this path requires OcteonTX2/CN20K hardware.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
36
EG Risk 36/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. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity70% × 45%
The EG Score, 7.0 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default: CISA has not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

July 24, 2026

Last Modified

August 11, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
Patch available.
generic

octeontx2-pf: avoid double free of pool->stack on AQ init failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-pf: avoid double free of pool->stack on AQ init failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-pf: avoid double free of pool->stack on AQ init failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-pf: avoid double free of pool->stack on AQ init failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b244c242bec48b37e82b89787afd6a4c43457e1
generic

octeontx2-pf: avoid double free of pool->stack on AQ init failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94192b0579333c3deee2441379aab8ca98fc2e6b
generic

octeontx2-pf: avoid double free of pool->stack on AQ init failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c29603498b05c049dbbbc47e882f2fbf0193cd7
generic

octeontx2-pf: avoid double free of pool->stack on AQ init failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d9b9d7dbef976ae7f855b6358f1d703014e96ea
generic

octeontx2-pf: avoid double free of pool->stack on AQ init failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0488a0bb344fb1992853b60082acff6be8164d74

Vendor Advisories for CVE-2026-64222(1)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-04ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-04ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-04ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-04ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-04ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-04ubuntu

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 rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Weakness Classification(1)

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

All Vendor Advisories

(6)

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 7× in last 7d / 79× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 308 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 208 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64222?
CVE-2026-64222 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: avoid double free of pool->stack on AQ init failure otx2poolaq_init() frees pool->stack when mailbox sync or retry allocation fails, but leaves the pointer unchanged. Later, otx2sqaurapoolinit() unwinds the partial…
When was the CVE record for CVE-2026-64222 published?
The CVE record for CVE-2026-64222 was published on July 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 11, 2026; the record at its source may have been updated since.
Is CVE-2026-64222 actively exploited?
CVE-2026-64222 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64222?
CVE-2026-64222 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64222?
A fix for CVE-2026-64222 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64222 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64222

Explore →

Is Your Infrastructure Affected by CVE-2026-64222?

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

Book a Demo →Browse All CVEs