CVE-2026-64122

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.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: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover

mlx5e_tx_reporter_timeout_recover() accesses sq->netdev after mlx5e_safe_reopen_channels() has torn down and freed the channel (and its embedded SQs). Replace the three sq->netdev references with priv->netdev which is safe because priv outlives channel teardown.

The netdev_err() call already used priv->netdev for this reason; make the trylock/unlock and health_channel_eq_recover calls consistent.

This fixes the following KASAN splat:

BUG: KASAN: use-after-free in mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core] Read of size 8 at addr ffff889860ed0b28 by task kworker/u113:2/5277

Call Trace: mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core] devlink_health_reporter_recover+0xa2/0x150 devlink_health_report+0x254/0x7c0 mlx5e_reporter_tx_timeout+0x297/0x380 [mlx5_core] mlx5e_tx_timeout_work+0x109/0x170 [mlx5_core] process_one_work+0x677/0xf20 worker_thread+0x51f/0xd90 kthread+0x3a5/0x810 ret_from_fork+0x208/0x400 ret_from_fork_asm+0x1a/0x30

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

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (3)

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

net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d260c5d2d89eb2c8c528d54b576b3aae3e20231
generic

net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1604a2d68414aa4cc34faac0b7faa9c14455e8d3
generic

net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/152295aa7dc2c5e046606f7dadc84fce41136446

Vendor Advisories for CVE-2026-64122(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

Weakness Classification(1)

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

All Vendor Advisories

(5)

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 62× in last 7d / 370× 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 449 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64122?
CVE-2026-64122 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix use-after-free in mlx5etxreportertimeoutrecover mlx5etxreportertimeoutrecover() accesses sq->netdev after mlx5esafereopen_channels() has torn down and freed the channel (and its embedded SQs). Replace the three…
When was CVE-2026-64122 disclosed?
CVE-2026-64122 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-64122 actively exploited?
CVE-2026-64122 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 61.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64122?
CVE-2026-64122 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64122?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64122, 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-64122

Explore →

Is Your Infrastructure Affected by CVE-2026-64122?

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

Start Free Scan →Browse All CVEs