Vulnerability · Published May 6, 2026 · Assigned by Linux

CVE-2026-43167xfrm: always flush state and policy upon NETDEV_UNREGISTER event

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.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.0% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: xfrm: always flush state and policy upon NETDEV_UNREGISTER event syzbot is reporting that "struct xfrm_state" refcount is leaking. unregister_netdevice: waiting for netdevsim0 to become free. Usage count = 2 ref_tracker: netdev@ffff888052f24618 has 1/1 users at __netdev_tracker_alloc include/linux/netdevice.h:4400 [inline] netdev_tracker_alloc include/linux/netdevice.h:4412 [inline] xfrm_dev_state_add+0x3a5/0x1080 net/xfrm/xfrm_device.c:316 xfrm_state_construct net/xfrm/xfrm_user.c:986 [inline] xfrm_add_sa+0x34ff/0x5fa0 net/xfrm/xfrm_user.c:1022 xfrm_user_rcv_msg+0x58e/0xc00 net/xfrm/xfrm_user.c:3507 netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2550 xfrm_netlink_rcv+0x71/0x90 net/xfrm/xfrm_user.c:3529 netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline] netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1344 netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1894 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg net/socket.c:742 [inline] ____sys_sendmsg+0xa5d/0xc30 net/socket.c:2592 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2646 __sys_sendmsg+0x16d/0x220 net/socket.c:2678 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f This is because commit d77e38e612a0 ("xfrm: Add an IPsec hardware offloading API") implemented xfrm_dev_unregister() as no-op despite xfrm_dev_state_add() from xfrm_state_construct() acquires a reference to "struct net_device". I guess that that commit expected that NETDEV_DOWN event is fired before NETDEV_UNREGISTER event fires, and also assumed that xfrm_dev_state_add() is called only if (dev->features & NETIF_F_HW_ESP) != 0. Sabrina Dubroca identified steps to reproduce the same symptoms as below. echo 0 > /sys/bus/netdevsim/new_device dev=$(ls -1 /sys/bus/netdevsim/devices/netdevsim0/net/) ip xfrm state add src 192.168.13.1 dst 192.168.13.2 proto esp \ spi 0x1000 mode tunnel aead 'rfc4106(gcm(aes))' $key 128 \ offload crypto dev $dev dir out ethtool -K $dev esp-hw-offload off echo 0 > /sys/bus/netdevsim/del_device Like these steps indicate, the NETIF_F_HW_ESP bit can be cleared after xfrm_dev_state_add() acquired a reference to "struct net_device". Also, xfrm_dev_state_add() does not check for the NETIF_F_HW_ESP bit when acquiring a reference to "struct net_device". Commit 03891f820c21 ("xfrm: handle NETDEV_UNREGISTER for xfrm device") re-introduced the NETDEV_UNREGISTER event to xfrm_dev_event(), but that commit for unknown reason chose to share xfrm_dev_down() between the NETDEV_DOWN event and the NETDEV_UNREGISTER event. I guess that that commit missed the behavior in the previous paragraph. Therefore, we need to re-introduce xfrm_dev_unregister() in order to release the reference to "struct net_device" by unconditionally flushing state and policy.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-43167
Debian:13linux6.12.85-1DEBIAN-CVE-2026-43167
Debian:14linux6.19.6-1DEBIAN-CVE-2026-43167
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux6.8.0-134.134UBUNTU-CVE-2026-43167
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-aws6.8.0-1060.63UBUNTU-CVE-2026-43167
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-azure6.8.0-1063.71UBUNTU-CVE-2026-43167
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1062.69UBUNTU-CVE-2026-43167
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-gcp6.8.0-1063.69UBUNTU-CVE-2026-43167
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-gke6.8.0-1058.64UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1045.48UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-ibm6.8.0-1060.61UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1060.61~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-134.134.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-134.134.1~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1058.61UBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1058.61~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1058.61.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1029.30UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-oracle6.8.0-1057.58UBUNTU-CVE-2026-43167
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1057.58~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-raspi6.8.0-1060.64UBUNTU-CVE-2026-43167
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43167
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43167
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-134.134~22.04.1UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-43167
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1032.33UBUNTU-CVE-2026-43167
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-43167

Affected products (as reported)

VendorProductVersions
Linux Linux d77e38e612a017480157fe6d2c1422f42cb5b7e3 – before d4df5a7da376e35089b8b601a86ff8a4cf997e2fd77e38e612a017480157fe6d2c1422f42cb5b7e3 – before 166801e49a5b5fc127b8c9e2f110f303cfddfbc3d77e38e612a017480157fe6d2c1422f42cb5b7e3 – before a3c8fede034fa27892f87c863cbd5493167d17edd77e38e612a017480157fe6d2c1422f42cb5b7e3 – before 59581778792cbaf8ad788f4a21dc663ce986050ed77e38e612a017480157fe6d2c1422f42cb5b7e3 – before 8c75c455ecd3bfd2f36abf66edb7021c4fa19ec4d77e38e612a017480157fe6d2c1422f42cb5b7e3 – before 4efa91a28576054aae0e6dad9cba8fed8293aef8
Linux Linux 4.12

References