Heimdall Security Logo

CVE-2026-64125

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.6%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, 3.19, 0, <9a1730245e416d11ad5c0f2c100061d61cc43f60, 5.15.209, 6.12.92, 6.6.142, <=5.10.*, <=6.6.*, 6.1.175, <49bdf6bbb21b9c6e3f4d0c1910bf0ef98424be95, <2040eb83f6ada148fb32dd98b943a498005d79f2, 6.18.34, 7.1, <=6.18.*, <f2782ddac82c70df313012da5f71f1f06b5553ca, 7.0.11, <a212fc08f5c48a16a94092bf0a9a8b7cf4483b11, <b579f3a73da7a7e74213558f4cc3d865c30aaa78, 5.10.258, <=*, <=5.15.*, <3d4ef05266ab16d8ef7dd21658a557801eb78704, 6ef398ea60d931b97d69ed080bd0bd00fac38ec6, <3.19, <289499907399c5a9f2ed82cb34df49112bb8488f

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.

Gravité et risque d'exploitation

CVE-2026-64125 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.55 %, ce qui la place devant 45.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, 3.19, 0, <9a1730245e416d11ad5c0f2c100061d61cc43f60, 5.15.209, 6.12.92, 6.6.142, <=5.10.*, <=6.6.*, 6.1.175, <49bdf6bbb21b9c6e3f4d0c1910bf0ef98424be95, <2040eb83f6ada148fb32dd98b943a498005d79f2, 6.18.34, 7.1, <=6.18.*, <f2782ddac82c70df313012da5f71f1f06b5553ca, 7.0.11, <a212fc08f5c48a16a94092bf0a9a8b7cf4483b11, <b579f3a73da7a7e74213558f4cc3d865c30aaa78, 5.10.258, <=*, <=5.15.*, <3d4ef05266ab16d8ef7dd21658a557801eb78704, 6ef398ea60d931b97d69ed080bd0bd00fac38ec6, <3.19, <289499907399c5a9f2ed82cb34df49112bb8488f) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE