Vulnerability · Published Dec 29, 2024 · Assigned by Linux
CVE-2024-56751ipv6: release nexthop on device removal
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: ipv6: release nexthop on device removal The CI is hitting some aperiodic hangup at device removal time in the pmtu.sh self-test: unregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6 ref_tracker: veth_A-R1@ffff888013df15d8 has 1/5 users at dst_init+0x84/0x4a0 dst_alloc+0x97/0x150 ip6_dst_alloc+0x23/0x90 ip6_rt_pcpu_alloc+0x1e6/0x520 ip6_pol_route+0x56f/0x840 fib6_rule_lookup+0x334/0x630 ip6_route_output_flags+0x259/0x480 ip6_dst_lookup_tail.constprop.0+0x5c2/0x940 ip6_dst_lookup_flow+0x88/0x190 udp_tunnel6_dst_lookup+0x2a7/0x4c0 vxlan_xmit_one+0xbde/0x4a50 [vxlan] vxlan_xmit+0x9ad/0xf20 [vxlan] dev_hard_start_xmit+0x10e/0x360 __dev_queue_xmit+0xf95/0x18c0 arp_solicit+0x4a2/0xe00 neigh_probe+0xaa/0xf0 While the first suspect is the dst_cache, explicitly tracking the dst owing the last device reference via probes proved such dst is held by the nexthop in the originating fib6_info. Similar to commit f5b51fe804ec ("ipv6: route: purge exception on removal"), we need to explicitly release the originating fib info when disconnecting a to-be-removed device from a live ipv6 dst: move the fib6_info cleanup into ip6_dst_ifdown(). Tested running: ./pmtu.sh cleanup_ipv6_exception in a tight loop for more than 400 iterations with no spat, running an unpatched kernel I observed a splat every ~10 iterations.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.123-1 | DEBIAN-CVE-2024-56751 |
| Debian:13 | linux | 6.12.3-1 | DEBIAN-CVE-2024-56751 |
| Debian:14 | linux | 6.12.3-1 | DEBIAN-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux | 5.15.0-144.157 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux | 5.15.0-144.157 | USN-7654-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-58.60 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1088.95 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1088.95 | USN-7654-1 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1027.29 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1027.29~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1094.103 | USN-7711-1 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1094.103 | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1027.32 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1012.12~24.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1027.32~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1094.103.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1014.15 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1087.96 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1087.96 | USN-7654-1 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1028.30 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1011.11~24.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1028.30~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1085.91 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1085.91 | USN-7654-1 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1023.27 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1070.78 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1070.78 | USN-7654-1 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1010.12 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-58.60~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1080.83 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1080.83 | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1024.24 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1024.24~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1083.89 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1083.89 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1084.89 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1084.89 | USN-7654-4 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-144.157 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-144.157 | USN-7654-1 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-58.60.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-58.60.1~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1082.83 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1082.83 | USN-7654-1 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1026.29 | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | 6.11.0-1007.7 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1026.29~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1026.29.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1041.41 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1041.41 | USN-7654-1 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1008.8 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1030.30 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1030.30 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1015.15 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1026.26 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1085.91 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1085.91 | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1024.25 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1024.25~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1083.86 | USN-7686-1 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1083.86 | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1028.32 | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-58.60.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-58.60.1~22.04.1 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-56751 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1017.18 | UBUNTU-CVE-2024-56751 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1052.56 | USN-7654-5 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1052.56 | UBUNTU-CVE-2024-56751 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74 – before 77aa9855a878fb43f547ddfbda3127a1e88ad31af88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74 – before b2f26a27ea3f72f75d18330f76f5d1007c791848f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74 – before 43e25adc80269f917d2a195f0d59f74cdd182955f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74 – before a3c3f8a4d025acc8c857246ec2b812c59102487af88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74 – before 0e4c6faaef8a24b762a24ffb767280e263ef8e10f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74 – before eb02688c5c45c3e7af7e71f036a7144f5639cbfe |
| Linux | Linux | 5.3 |
References
- https://git.kernel.org/stable/c/77aa9855a878fb43f547ddfbda3127a1e88ad31a
- https://git.kernel.org/stable/c/b2f26a27ea3f72f75d18330f76f5d1007c791848
- https://git.kernel.org/stable/c/43e25adc80269f917d2a195f0d59f74cdd182955
- https://git.kernel.org/stable/c/a3c3f8a4d025acc8c857246ec2b812c59102487a
- https://git.kernel.org/stable/c/0e4c6faaef8a24b762a24ffb767280e263ef8e10
- https://git.kernel.org/stable/c/eb02688c5c45c3e7af7e71f036a7144f5639cbfe
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html