Heimdall Security Logo

CVE-2026-98306

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 0, <f8fb4738ccef5f9d107845b05734a56352747b1a, <ddf60220c925b54a1714c4722fdbdb12833232d0, 6.12.112, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <e4d7c52f15f572608374947c6c802052e1a2fc82, <5130afa025c95faa621adf8bac525baeb2b290d2, <7616242a2b37883f7322aaa1d2bd6cd0fed28315, 891ef8dd2a8d14e4e73a81dcdb135b574c57f556, <1d9f5c78903dd25a3556229eb716dd465c5f3573, 7.2.8, <=6.18.*, 5.15.222, <8c16e1ccc082a3763dfc6bc2d3f658c1a6336f9d, <=7.2.*, <72f410616000d21a0a6ec6c93a60301b9c92e95c, <=*, <4.14, <=5.15.*, 6.18.54, 4.14, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation When an SRv6 packet arrives on an interface enslaved to a VRF, vrf_ip6_rcv() sets IP6SKB_L3SLAVE in IP6CB, but decap_and_validate() has never set IPSKB_L3SLAVE in IPCB. The bit stayed clear in the common case, and with CONFIG_IPV6_MIP6 the leftover frag_max_size of a reassembled outer packet could even set it, with no VRF involved. Commit 44930446dde4 ("ipv6: seg6: clear IPv4 control block on IPIP decapsulation") then made the unreliable bit reliably clear. The effect of the missing flag is visible with End.DX4 when a delivery to a local address of the node reaches the socket lookup. For example, a UDP socket bound to the enslaved ingress interface does not receive any of the decapsulated packets, while an unbound socket outside the VRF does. This contradicts Documentation/networking/vrf.rst: by default the scope of an unbound UDP or TCP socket is limited to the default VRF. Set IPSKB_L3SLAVE for IPv4 in decap_and_validate(), which already does the same for IPv6. The socket lookup then matches the decapsulated packet like any other packet received on that enslaved interface. Such a packet matches an unbound UDP or TCP socket only when udp_l3mdev_accept or tcp_l3mdev_accept is set.

Gravité et risque d'exploitation

CVE-2026-98306 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.18 %, ce qui la place devant 7.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 0, <f8fb4738ccef5f9d107845b05734a56352747b1a, <ddf60220c925b54a1714c4722fdbdb12833232d0, 6.12.112, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <e4d7c52f15f572608374947c6c802052e1a2fc82, <5130afa025c95faa621adf8bac525baeb2b290d2, <7616242a2b37883f7322aaa1d2bd6cd0fed28315, 891ef8dd2a8d14e4e73a81dcdb135b574c57f556, <1d9f5c78903dd25a3556229eb716dd465c5f3573, 7.2.8, <=6.18.*, 5.15.222, <8c16e1ccc082a3763dfc6bc2d3f658c1a6336f9d, <=7.2.*, <72f410616000d21a0a6ec6c93a60301b9c92e95c, <=*, <4.14, <=5.15.*, 6.18.54, 4.14, 7.3) 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