CVE-2026-64118

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

qed: fix double free in qed_cxt_tables_alloc()

If one of the later PF or VF CID bitmap allocations fails, qed_cid_map_alloc() jumps to cid_map_fail and frees the previously allocated CID bitmaps before returning an error. qed_cxt_tables_alloc() then calls qed_cxt_mngr_free(), which invokes qed_cid_map_free() again.

Fix this by setting each CID bitmap pointer to NULL after bitmap_free() to avoid double free.

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 reproduction was not attempted because exercising the failing allocation path requires device-specific setup.

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

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (8)

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

qed: fix double free in qed_cxt_tables_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

qed: fix double free in qed_cxt_tables_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

qed: fix double free in qed_cxt_tables_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

qed: fix double free in qed_cxt_tables_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb
generic

qed: fix double free in qed_cxt_tables_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3904b993cc17ec5d7c5d3b57dbd0b775dafb9684
generic

qed: fix double free in qed_cxt_tables_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

qed: fix double free in qed_cxt_tables_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

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

qed: fix double free in qed_cxt_tables_alloc() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227

Vendor Advisories for CVE-2026-64118(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1059.60~22.04.1) @ jammy2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1067.75) @ noble2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu

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 (141 versions)7.0.12-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 20× in last 7d / 96× 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 255 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64118?
CVE-2026-64118 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: qed: fix double free in qedcxttables_alloc() If one of the later PF or VF CID bitmap allocations fails, qedcidmapalloc() jumps to cidmap_fail and frees the previously allocated CID bitmaps before returning an error.…
When was CVE-2026-64118 disclosed?
CVE-2026-64118 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64118 actively exploited?
CVE-2026-64118 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 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64118?
CVE-2026-64118 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-64118?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64118, 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-64118

Explore →

Is Your Infrastructure Affected by CVE-2026-64118?

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

Start Free Scan →Browse All CVEs