CVE-2026-64125
Linux Kernel vulnerability
- Published19 Jul 2026
Description
In the Linux kernel, the following vulnerability has been resolved: net: bcmgenet: keep RBUF EEE/PM disabled Setting RBUF_EEE_EN | RBUF_PM_EN in RBUF_ENERGY_CTRL breaks the RX path on GENET hardware once MAC EEE becomes active. RX traffic stops flowing while the link stays up and the usual descriptor/RX error counters remain quiet. In that state the MAC still accepts frames (rbuf_ovflow_cnt keeps climbing) but RBUF no longer forwards them to DMA, so rx_packets is no longer incremented at the netdev level. On some boards the corruption ends up as a paging fault in skb_release_data via bcmgenet_rx_poll on an LPI exit. Reproduced on Pi 4B (BCM2711 + BCM54213PE) and confirmed by Florian Fainelli on an internal Broadcom 4908-family board with the same crash signature. RBUF_PM_EN is not publicly documented. This shows up more often now that phy_support_eee() enables EEE by default, but it also affects older kernels as soon as TX LPI is turned on via ethtool, so it is not specific to recent changes. Always clear RBUF_EEE_EN | RBUF_PM_EN in bcmgenet_eee_enable_set so the bits stay off across resets. UMAC and TBUF setup is left alone so TX-side EEE keeps working.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
- https://git.kernel.org/stable/c/2040eb83f6ada148fb32dd98b943a498005d79f2
- https://git.kernel.org/stable/c/289499907399c5a9f2ed82cb34df49112bb8488f
- https://git.kernel.org/stable/c/3d4ef05266ab16d8ef7dd21658a557801eb78704
- https://git.kernel.org/stable/c/49bdf6bbb21b9c6e3f4d0c1910bf0ef98424be95
- https://git.kernel.org/stable/c/9a1730245e416d11ad5c0f2c100061d61cc43f60
- https://git.kernel.org/stable/c/a212fc08f5c48a16a94092bf0a9a8b7cf4483b11
References
- https://git.kernel.org/stable/c/2040eb83f6ada148fb32dd98b943a498005d79f2
- https://git.kernel.org/stable/c/289499907399c5a9f2ed82cb34df49112bb8488f
- https://git.kernel.org/stable/c/3d4ef05266ab16d8ef7dd21658a557801eb78704
- https://git.kernel.org/stable/c/49bdf6bbb21b9c6e3f4d0c1910bf0ef98424be95
- https://git.kernel.org/stable/c/9a1730245e416d11ad5c0f2c100061d61cc43f60
- https://git.kernel.org/stable/c/a212fc08f5c48a16a94092bf0a9a8b7cf4483b11
- https://git.kernel.org/stable/c/b579f3a73da7a7e74213558f4cc3d865c30aaa78
- https://git.kernel.org/stable/c/f2782ddac82c70df313012da5f71f1f06b5553ca
Frequently asked
Is CVE-2026-64125 being actively exploited?
CVE-2026-64125 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.55%.
How severe is CVE-2026-64125?
CVE-2026-64125 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.55% probability of exploitation.
Which products are affected by CVE-2026-64125?
Affected products include Linux Kernel.
How do I fix CVE-2026-64125?
Upgrade affected software to a fixed version, for example Linux Kernel 5.10.258 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-64125 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.