CVE-2026-64055
What it is
In the Linux kernel, the following vulnerability has been resolved: net: ethernet: cortina: Carry over frag counter The gmac_rx() NAPI poll function assembles packets in an SKB from a ring buffer. If the ring buffer gets completely emptied during a poll cycle, we exit gmac_rx(), but the packet is not yet completely assembled in the SKB, yet the fragment counter frag_nr is reset to zero on the next invocation. Solve this by making the RX fragment counter a part of the port struct, and carry it over between invocations. Reset the fragment counter only right after calling napi_gro_frags(), on error (after calling napi_free_frags()) or if stopping the port. Reset it in some place where not strictly necessary just to emphasize what is going on. This was found by Sashiko during normal patch review.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.5% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.258
- Linux Kernel < 5.15.209
- Linux Kernel < 6.1.175
- Linux Kernel < 6.6.142
- Linux Kernel < 6.12.92
- Linux Kernel < 6.18.34
- Linux Kernel < 7.0.11
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-64055.md and follow it. Check whether this project is affected by CVE-2026-64055. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/46806096f35b8d3dfa2f321ddd77f597edcdb85f
- https://git.kernel.org/stable/c/7123cf481e21b54eb6adc4cb0d8dc2876aeaee41
- https://git.kernel.org/stable/c/75105fcf73f1ce7d9f769aaefec6e6d6645d5ac0
- https://git.kernel.org/stable/c/78cf08b3be47c28f07008a76c932bad7cdffa9d8
- https://git.kernel.org/stable/c/7af1fabdee744b7995fe01b30b77dfc397657cb5
- https://git.kernel.org/stable/c/c373b34877afea61c89e0dd2e38948c624249b9b
- https://git.kernel.org/stable/c/df31e3b64455293df1ea89c7da7d5c9bfbcdd253
- https://git.kernel.org/stable/c/ebd8ec2b309e3a447851b456ccaf8fb39f3661e7
References
- https://git.kernel.org/stable/c/46806096f35b8d3dfa2f321ddd77f597edcdb85f
- https://git.kernel.org/stable/c/7123cf481e21b54eb6adc4cb0d8dc2876aeaee41
- https://git.kernel.org/stable/c/75105fcf73f1ce7d9f769aaefec6e6d6645d5ac0
- https://git.kernel.org/stable/c/78cf08b3be47c28f07008a76c932bad7cdffa9d8
- https://git.kernel.org/stable/c/7af1fabdee744b7995fe01b30b77dfc397657cb5
- https://git.kernel.org/stable/c/c373b34877afea61c89e0dd2e38948c624249b9b
- https://git.kernel.org/stable/c/df31e3b64455293df1ea89c7da7d5c9bfbcdd253
- https://git.kernel.org/stable/c/ebd8ec2b309e3a447851b456ccaf8fb39f3661e7