CVE-2026-64125

CVE CVE-2026-64125EUVD EUVD-2026-45810Published 2026-07-19T15:40:22.000ZLast changed 2026-08-05T12:39:31.000ZCVSS 9.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 6.18.34; 6ef398ea60d931b97d69ed080bd0bd00fac38ec6 <9a1730245e416d11ad5c0f2c100061d61cc43f60; 6ef398ea60d931b97d69ed080bd0bd00fac38ec6 <a212fc08f5c48a16a94092bf0a9a8b7cf4483b11; patch: 7.1; 6ef398ea60d931b97d69ed080bd0bd00fac38ec6 <b579f3a73da7a7e74213558f4cc3d865c30aaa78; patch: 6.1.175; patch: 6.12.92; 6ef398ea60d931b97d69ed080bd0bd00fac38ec6 <289499907399c5a9f2ed82cb34df49112bb8488f; 6ef398ea60d931b97d69ed080bd0bd00fac38ec6 <49bdf6bbb21b9c6e3f4d0c1910bf0ef98424be95; 6ef398ea60d931b97d69ed080bd0bd00fac38ec6 <3d4ef05266ab16d8ef7dd21658a557801eb78704; patch: 0; 3.19; patch: 6.6.142; patch: 5.10.258; 6ef398ea60d931b97d69ed080bd0bd00fac38ec6 <f2782ddac82c70df313012da5f71f1f06b5553ca; 6ef398ea60d931b97d69ed080bd0bd00fac38ec6 <2040eb83f6ada148fb32dd98b943a498005d79f2; patch: 7.0.11; patch: 5.15.209

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.