Heimdall Security Logo

CVE-2026-46273

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

CVSS 8.6 · Élevée
EPSS 0.7%
Linux•Linux•Versions : <=6.1.*, 7.0.7, <=7.0.*, <=6.12.*, <4.2, <1cdf5dbcec988d06f5f720bdf89e91073f77fa10, 0, <3af24f0c4c31f18a4a2d927990759194832bb6e9, 6.12.88, <82bc89fbb82d9396fb4eaee8720ea85e2e787957, 5.15.209, <=5.10.*, 8641dd85799f85bef5f0d1f87356aaa12cb2195e, <=6.6.*, 6.1.175, <db8012c631cb845e9ae2b4b531e17d86c9519755, <c1f261863e65b508f37416dfbc5c5d911c9b9233, 7.1, <=6.18.*, <9a5e984d7af910e46dcbed3ce77873e000a4f77d, 5.10.258, 4.2, <86fc64584811d43c9ccd74447de58620189d8b77, <cc427d24ac6442ffdeafd157a63c7c5b73ed4de4, <=*, <=5.15.*, 6.6.140, 6.18.30

Description

In the Linux kernel, the following vulnerability has been resolved: ibmveth: Disable GSO for packets with small MSS Some physical adapters on Power systems do not support segmentation offload when the MSS is less than 224 bytes. Attempting to send such packets causes the adapter to freeze, stopping all traffic until manually reset. Implement ndo_features_check to disable GSO for packets with small MSS values. The network stack will perform software segmentation instead. The 224-byte minimum matches ibmvnic commit <f10b09ef687f> ("ibmvnic: Enforce stronger sanity checks on GSO packets") which uses the same physical adapters in SEA configurations. The issue occurs specifically when the hardware attempts to perform segmentation (gso_segs > 1) with a small MSS. Single-segment GSO packets (gso_segs == 1) do not trigger the problematic LSO code path and are transmitted normally without segmentation. Add an ndo_features_check callback to disable GSO when MSS < 224 bytes. Also call vlan_features_check() to ensure proper handling of VLAN packets, particularly QinQ (802.1ad) configurations where the hardware parser may not support certain offload features. Validated using iptables to force small MSS values. Without the fix, the adapter freezes. With the fix, packets are segmented in software and transmission succeeds. Comprehensive regression testing completedd (MSS tests, performance, stability).

Gravité et risque d'exploitation

CVE-2026-46273 obtient un score CVSS de 8.6/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.72 %, ce qui la place devant 52.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 7.0.7, <=7.0.*, <=6.12.*, <4.2, <1cdf5dbcec988d06f5f720bdf89e91073f77fa10, 0, <3af24f0c4c31f18a4a2d927990759194832bb6e9, 6.12.88, <82bc89fbb82d9396fb4eaee8720ea85e2e787957, 5.15.209, <=5.10.*, 8641dd85799f85bef5f0d1f87356aaa12cb2195e, <=6.6.*, 6.1.175, <db8012c631cb845e9ae2b4b531e17d86c9519755, <c1f261863e65b508f37416dfbc5c5d911c9b9233, 7.1, <=6.18.*, <9a5e984d7af910e46dcbed3ce77873e000a4f77d, 5.10.258, 4.2, <86fc64584811d43c9ccd74447de58620189d8b77, <cc427d24ac6442ffdeafd157a63c7c5b73ed4de4, <=*, <=5.15.*, 6.6.140, 6.18.30) 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