Heimdall Security Logo

CVE-2024-26803

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c, <=6.1.*, 5.15.151, <8f7a3894e58e6f5d5815533cfde60e3838947941, <5.13, 0, <fe9f801355f0b47668419f30f1fac1cf4539e736, <f011c103e654d83dc85f057a7d1bd0960d02831c, 6.8, 6.1.81, <=6.6.*, 5.13, <7985d73961bbb4e726c1be7b9cd26becc7be8325, <16edf51f33f52dff70ed455bc40a6cc443c04664, <=*, <=5.15.*, <=6.7.*, 6.6.21, 6.7.9

Description

In the Linux kernel, the following vulnerability has been resolved: net: veth: clear GRO when clearing XDP even when down veth sets NETIF_F_GRO automatically when XDP is enabled, because both features use the same NAPI machinery. The logic to clear NETIF_F_GRO sits in veth_disable_xdp() which is called both on ndo_stop and when XDP is turned off. To avoid the flag from being cleared when the device is brought down, the clearing is skipped when IFF_UP is not set. Bringing the device down should indeed not modify its features. Unfortunately, this means that clearing is also skipped when XDP is disabled _while_ the device is down. And there's nothing on the open path to bring the device features back into sync. IOW if user enables XDP, disables it and then brings the device up we'll end up with a stray GRO flag set but no NAPI instances. We don't depend on the GRO flag on the datapath, so the datapath won't crash. We will crash (or hang), however, next time features are sync'ed (either by user via ethtool or peer changing its config). The GRO flag will go away, and veth will try to disable the NAPIs. But the open path never created them since XDP was off, the GRO flag was a stray. If NAPI was initialized before we'll hang in napi_disable(). If it never was we'll crash trying to stop uninitialized hrtimer. Move the GRO flag updates to the XDP enable / disable paths, instead of mixing them with the ndo_open / ndo_close paths.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions d3256efd8e8b234a6251e4d4580bd2c3c31fdc4c, <=6.1.*, 5.15.151, <8f7a3894e58e6f5d5815533cfde60e3838947941, <5.13, 0, <fe9f801355f0b47668419f30f1fac1cf4539e736, <f011c103e654d83dc85f057a7d1bd0960d02831c, 6.8, 6.1.81, <=6.6.*, 5.13, <7985d73961bbb4e726c1be7b9cd26becc7be8325, <16edf51f33f52dff70ed455bc40a6cc443c04664, <=*, <=5.15.*, <=6.7.*, 6.6.21, 6.7.9) 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