Remote kernel memory corruption via fragment counter reset
Published Jul 19, 2026 · Updated Jul 19, 2026
Memory corruption in the Cortina Gemini GMAC driver in affected Linux releases allows remote attackers to corrupt kernel memory via Ethernet frames. When gmac_rx() drains the receive ring before completing an SKB, the next poll resets frag_nr to zero instead of preserving the partial packet's fragment index. Unauthenticated Ethernet traffic reaches the faulty receive path only on systems using this driver, where fragment-slot reuse corrupts kernel state or triggers a panic.
Summary
What happened
Memory corruption in the Cortina Gemini GMAC driver in affected Linux releases allows remote attackers to corrupt kernel memory via Ethernet frames. When gmac_rx() drains the receive ring before completing an SKB, the next poll resets frag_nr to zero instead of preserving the partial packet's fragment index. Unauthenticated Ethernet traffic reaches the faulty receive path only on systems using this driver, where fragment-slot reuse corrupts kernel state or triggers a panic.
The record
- CVE
- CVE-2026-64055
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.16
- Affected versionversion=4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 <46806096f35b8d3dfa2f321ddd77f597edcdb85f
- Affected versionversion=4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 <7123cf481e21b54eb6adc4cb0d8dc2876aeaee41
- Affected versionversion=4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 <75105fcf73f1ce7d9f769aaefec6e6d6645d5ac0
- Affected versionversion=4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 <78cf08b3be47c28f07008a76c932bad7cdffa9d8
- Affected versionversion=4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 <7af1fabdee744b7995fe01b30b77dfc397657cb5
- Affected versionversion=4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 <c373b34877afea61c89e0dd2e38948c624249b9b
- Affected versionversion=4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 <df31e3b64455293df1ea89c7da7d5c9bfbcdd253
- Affected versionversion=4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 <ebd8ec2b309e3a447851b456ccaf8fb39f3661e7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo