CVE-2026-64224

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-pf: fix double free in rvu_rep_rsrc_init()

rvu_rep_rsrc_init() allocates queue memory before calling otx2_init_hw_resources(). When hardware resource setup fails, otx2_init_hw_resources() already unwinds the partially initialized SQ, CQ, and aura state before returning an error. The representor error path then calls otx2_free_hw_resources() again and can free the same resources a second time.

Fix this by splitting the cleanup labels so that a failure from otx2_init_hw_resources() only releases queue memory. Keep the otx2_free_hw_resources() call for failures that happen after hardware resource initialization completed successfully.

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 representor hardware.

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 (3)

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

octeontx2-pf: fix double free in rvu_rep_rsrc_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-pf: fix double free in rvu_rep_rsrc_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-pf: fix double free in rvu_rep_rsrc_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8864b664d0443ecb8e56690e5546fcda5fe5e81b

Vendor Advisories for CVE-2026-64224(1)

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

Patch Availability(4)

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(4)

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 27× in last 7d / 122× 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 218 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64224?
CVE-2026-64224 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: fix double free in rvureprsrc_init() rvureprsrc_init() allocates queue memory before calling otx2inithw_resources(). When hardware resource setup fails, otx2inithw_resources() already unwinds the partially initialized…
When was CVE-2026-64224 disclosed?
CVE-2026-64224 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-64224 actively exploited?
CVE-2026-64224 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64224?
CVE-2026-64224 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64224?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64224, 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-64224

Explore →

Is Your Infrastructure Affected by CVE-2026-64224?

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