CVE-2026-64122
Use-after-free in Linux mlx5 driver can crash or enable kernel compromise.
Is CVE-2026-64122 being exploited?
Not confirmed. CVE-2026-64122 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-64122?
CVE-2026-64122 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64122?
Yes. A fix has been recorded for CVE-2026-64122. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64122 affect?
CVE-2026-64122 affects Linux kernel (mlx5 / mlx5_core), Mellanox/NVIDIA ConnectX NICs, Servers using mlx5 driver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64122?
Update Linux kernel to patched mlx5 release and reboot affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Triggerable use-after-free in mlx5 kernel driver can cause kernel crashes (DoS) and may enable local privilege escalation or arbitrary kernel code execution.
Immediate action required
- affected>= 4329514c61abefe4961541b128c549b017bab5ad and < 1604a2d68414aa4cc34faac0b7faa9c14455e8d3
- affected>= 83ac0304a2d77519dae1e54c9713cbe1aedf19c9 and < 152295aa7dc2c5e046606f7dadc84fce41136446
- affected>= 83ac0304a2d77519dae1e54c9713cbe1aedf19c9 and < 7d260c5d2d89eb2c8c528d54b576b3aae3e20231
- affected63f9d5fb4d8040077df801ca3270e2f02d55e0d9
- affected>= 6.18.14 and < 6.18.34
- affected>= 6.19.4 and < 6.20
- affected7.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.