Heimdall Security Logo

CVE-2026-31419

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <5.11, <=6.1.*, f1d206181f19b00b275b258fea1418718a2f4173, <=6.12.*, 5.16.3, <d4cc7e4c80b1634c7b1497574a2fdb18df6c026c, 0, 7.0, 4e5bd03ae34652cd932ab4c91c71c511793df75c, <5.17, <f5b94654a4a19891a8108d66ef166de6c028c6cd, c1f1691ef84fa6d38fa5e5148eca073145e97ffa, <=6.6.*, 5.15.17, 6.12.95, <a0f661918edc79d7a75e468128af8d41e2a1a83a, 5.10.94, <=6.19.*, 20949c3816463e97c6f8fe84c0280c7e5ae83a8d, <5.16, <=6.18.*, 6.1.184, <2884bf72fb8f03409e423397319205de48adca16, <=*, <2de5c8eea0a9db99dae7c36f4b541b74b41d3a04, 6.6.143, 6.18.22, 5.17, <00752893f96b344f258c9c6de18b33171ac4872c, 6.19.12

Description

In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix use-after-free in bond_xmit_broadcast() bond_xmit_broadcast() reuses the original skb for the last slave (determined by bond_is_last_slave()) and clones it for others. Concurrent slave enslave/release can mutate the slave list during RCU-protected iteration, changing which slave is "last" mid-loop. This causes the original skb to be double-consumed (double-freed). Replace the racy bond_is_last_slave() check with a simple index comparison (i + 1 == slaves_count) against the pre-snapshot slave count taken via READ_ONCE() before the loop. This preserves the zero-copy optimization for the last slave while making the "last" determination stable against concurrent list mutations. The UAF can trigger the following crash: ================================================================== BUG: KASAN: slab-use-after-free in skb_clone Read of size 8 at addr ffff888100ef8d40 by task exploit/147 CPU: 1 UID: 0 PID: 147 Comm: exploit Not tainted 7.0.0-rc3+ #4 PREEMPTLAZY Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:123) print_report (mm/kasan/report.c:379 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:597) skb_clone (include/linux/skbuff.h:1724 include/linux/skbuff.h:1792 include/linux/skbuff.h:3396 net/core/skbuff.c:2108) bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5334) bond_start_xmit (drivers/net/bonding/bond_main.c:5567 drivers/net/bonding/bond_main.c:5593) dev_hard_start_xmit (include/linux/netdevice.h:5325 include/linux/netdevice.h:5334 net/core/dev.c:3871 net/core/dev.c:3887) __dev_queue_xmit (include/linux/netdevice.h:3601 net/core/dev.c:4838) ip6_finish_output2 (include/net/neighbour.h:540 include/net/neighbour.h:554 net/ipv6/ip6_output.c:136) ip6_finish_output (net/ipv6/ip6_output.c:208 net/ipv6/ip6_output.c:219) ip6_output (net/ipv6/ip6_output.c:250) ip6_send_skb (net/ipv6/ip6_output.c:1985) udp_v6_send_skb (net/ipv6/udp.c:1442) udpv6_sendmsg (net/ipv6/udp.c:1733) __sys_sendto (net/socket.c:730 net/socket.c:742 net/socket.c:2206) __x64_sys_sendto (net/socket.c:2209) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) </TASK> Allocated by task 147: Freed by task 147: The buggy address belongs to the object at ffff888100ef8c80 which belongs to the cache skbuff_head_cache of size 224 The buggy address is located 192 bytes inside of freed 224-byte region [ffff888100ef8c80, ffff888100ef8d60) Memory state around the buggy address: ffff888100ef8c00: fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc ffff888100ef8c80: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff888100ef8d00: fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ^ ffff888100ef8d80: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb ffff888100ef8e00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================

Gravité et risque d'exploitation

CVE-2026-31419 obtient un score CVSS de 7.8/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.18 %, ce qui la place devant 7.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <5.11, <=6.1.*, f1d206181f19b00b275b258fea1418718a2f4173, <=6.12.*, 5.16.3, <d4cc7e4c80b1634c7b1497574a2fdb18df6c026c, 0, 7.0, 4e5bd03ae34652cd932ab4c91c71c511793df75c, <5.17, <f5b94654a4a19891a8108d66ef166de6c028c6cd, c1f1691ef84fa6d38fa5e5148eca073145e97ffa, <=6.6.*, 5.15.17, 6.12.95, <a0f661918edc79d7a75e468128af8d41e2a1a83a, 5.10.94, <=6.19.*, 20949c3816463e97c6f8fe84c0280c7e5ae83a8d, <5.16, <=6.18.*, 6.1.184, <2884bf72fb8f03409e423397319205de48adca16, <=*, <2de5c8eea0a9db99dae7c36f4b541b74b41d3a04, 6.6.143, 6.18.22, 5.17, <00752893f96b344f258c9c6de18b33171ac4872c, 6.19.12) 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