CVE-2024-26690

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.5 · Élevée
EPSS 0.8%
Linux•Linux•Versions : 6.6.18, 133466c3bbe171f826294161db203f7670bb30c8, 6.6, 6.8, <=*, <9680b2ab54ba8d72581100e8c45471306101836e, <6.6, <e6af0f082a4b87b99ad033003be2a904a1791b3f, <=6.7.*, <38cc3c6dcc09dc3a1800b5ec22aef643ca11eab8, ff12183568e0531f6db935378a92237766ad080a, 6.1.160, <6.2, 0, <=6.6.*, 6.7.6

Description

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: protect updates of 64-bit statistics counters As explained by a comment in <linux/u64_stats_sync.h>, write side of struct u64_stats_sync must ensure mutual exclusion, or one seqcount update could be lost on 32-bit platforms, thus blocking readers forever. Such lockups have been observed in real world after stmmac_xmit() on one CPU raced with stmmac_napi_poll_tx() on another CPU. To fix the issue without introducing a new lock, split the statics into three parts: 1. fields updated only under the tx queue lock, 2. fields updated only during NAPI poll, 3. fields updated only from interrupt context, Updates to fields in the first two groups are already serialized through other locks. It is sufficient to split the existing struct u64_stats_sync so that each group has its own. Note that tx_set_ic_bit is updated from both contexts. Split this counter so that each context gets its own, and calculate their sum to get the total value in stmmac_get_ethtool_stats(). For the third group, multiple interrupts may be processed by different CPUs at the same time, but interrupts on the same CPU will not nest. Move fields from this group to a newly created per-cpu struct stmmac_pcpu_stats.

Gravité et risque d'exploitation

CVE-2024-26690 obtient un score CVSS de 7.5/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.84 %, ce qui la place devant 57.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.6.18, 133466c3bbe171f826294161db203f7670bb30c8, 6.6, 6.8, <=*, <9680b2ab54ba8d72581100e8c45471306101836e, <6.6, <e6af0f082a4b87b99ad033003be2a904a1791b3f, <=6.7.*, <38cc3c6dcc09dc3a1800b5ec22aef643ca11eab8, ff12183568e0531f6db935378a92237766ad080a, 6.1.160, <6.2, 0, <=6.6.*, 6.7.6) 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