CVE-2026-68127

Description

In the Linux kernel, the following vulnerability has been resolved: ila: reload IPv6 header after pskb_may_pull in checksum adjust ila_csum_adjust_transport() caches ip6h = ipv6_hdr(skb) before calling pskb_may_pull(). On a non-linear skb whose transport header sits in a page fragment, pskb_may_pull() can call __pskb_pull_tail() / pskb_expand_head() and free the old skb head, leaving ip6h dangling; the following get_csum_diff(ip6h, p) then reads freed memory. ila_update_ipv6_locator() uses ip6h (and the iaddr derived from it) again after the csum-adjust call and additionally writes the new locator through that pointer. Impact: a remote IPv6 packet routed through a configured ILA csum-adjust-transport route or receive-side mapping triggers a slab-use-after-free in ila_update_ipv6_locator() (KASAN). The route or mapping requires CAP_NET_ADMIN to configure, but trigger packets are unauthenticated once it exists. Reload ip6h after each pskb_may_pull() in ila_csum_adjust_transport() before the csum-diff read. In ila_update_ipv6_locator() only the ILA_CSUM_ADJUST_TRANSPORT case pulls the skb, so reload ip6h and iaddr in that case alone before the destination-address write; the neutral-map modes never pull and keep their cached pointers.

Gravité et risque d'exploitation

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

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, 7.2, <=6.12.*, 6.12.101, <e451a904606c571f731ef7a06b3398619dce5300, 0, <1eadcb43893b897ade85ac5bf5c618054bc3c655, <=7.1.*, 5.15.216, <c6a13ae00dab3a1a8c7cf2f843f0fc9e8d4b0ccc, <896a9512d0d83c2a4b357e5585b7b62a8e3f95c1, <=5.10.*, <=6.6.*, 6.18.42, 7.1.6, <4.5, 6.1.183, <ba353caafb06ccee57b78d3254e3cebf1dea4a93, <=6.18.*, <92d3817649df2b0b6a008a686c8275c88d7ef594, 33f11d16142b06588eedfc1dd8cf93790979a712, <=*, 4.5, <=5.15.*, <7097a0280b178237265681be66d1bef11d15894b, <472aba2603ca74c4f7722cb0c0296942b0776b8d, 5.10.265, 6.6.148) 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

• https://git.kernel.org/stable/c/e451a904606c571f731ef7a06b3398619dce5300
• https://git.kernel.org/stable/c/1eadcb43893b897ade85ac5bf5c618054bc3c655
• https://git.kernel.org/stable/c/ba353caafb06ccee57b78d3254e3cebf1dea4a93
• https://git.kernel.org/stable/c/896a9512d0d83c2a4b357e5585b7b62a8e3f95c1
• https://git.kernel.org/stable/c/7097a0280b178237265681be66d1bef11d15894b
• https://git.kernel.org/stable/c/472aba2603ca74c4f7722cb0c0296942b0776b8d
• https://git.kernel.org/stable/c/c6a13ae00dab3a1a8c7cf2f843f0fc9e8d4b0ccc
• https://git.kernel.org/stable/c/92d3817649df2b0b6a008a686c8275c88d7ef594