Linux kernel network driver bug affects widely deployed kernels and network appliances; can cause kernel memory corruption/DoS and may enable RCE—broad operational impact.
CVE-2026-64055
Linux cortina gmac RX frag counter bug enables kernel memory corruption via network packets
Is CVE-2026-64055 being exploited?
Not confirmed. CVE-2026-64055 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.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-64055?
CVE-2026-64055 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-64055?
Yes. A fix has been recorded for CVE-2026-64055. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64055 affect?
CVE-2026-64055 affects Linux kernel (cortina gmac driver), Embedded devices/SoCs using cortina gmac, Network appliances/routers with affected driver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64055?
Apply kernel/vendor patch immediately; block untrusted L2 traffic until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote memory corruption via crafted Ethernet frames leading to kernel crash, potential RCE or privilege escalation.
Immediate action required
- affected>= 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 and < df31e3b64455293df1ea89c7da7d5c9bfbcdd253
- affected>= 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 and < 7af1fabdee744b7995fe01b30b77dfc397657cb5
- affected>= 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 and < 75105fcf73f1ce7d9f769aaefec6e6d6645d5ac0
- affected>= 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 and < 78cf08b3be47c28f07008a76c932bad7cdffa9d8
- affected>= 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 and < 7123cf481e21b54eb6adc4cb0d8dc2876aeaee41
- affected>= 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 and < c373b34877afea61c89e0dd2e38948c624249b9b
- affected>= 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 and < 46806096f35b8d3dfa2f321ddd77f597edcdb85f
- affected>= 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 and < ebd8ec2b309e3a447851b456ccaf8fb39f3661e7
- affected4.16
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.