CVE-2026-43234: team: avoid NETDEV_CHANGEMTU event when unregistering slave
In the Linux kernel, the following vulnerability has been resolved:
team: avoid NETDEVCHANGEMTU event when unregistering slave
syzbot is reporting
unregisternetdevice: waiting for netdevsim0 to become free. Usage count = 3 reftracker: netdev@ffff88807dcf8618 has 1/2 users at netdevtrackeralloc include/linux/netdevice.h:4400 [inline] netdevhold include/linux/netdevice.h:4429 [inline] inetdevinit+0x201/0x4e0 net/ipv4/devinet.c:286 inetdevevent+0x251/0x1610 net/ipv4/devinet.c:1600 notifiercallchain+0x19d/0x3a0 kernel/notifier.c:85 callnetdevicenotifiersmtu net/core/dev.c:2318 [inline] netifsetmtuext+0x5aa/0x800 net/core/dev.c:9886 netifsetmtu+0xd7/0x1b0 net/core/dev.c:9907 devsetmtu+0x126/0x260 net/core/devapi.c:248 teamportdel+0xb07/0xcb0 drivers/net/team/teamcore.c:1333 teamdelslave drivers/net/team/teamcore.c:1936 [inline] teamdeviceevent+0x207/0x5b0 drivers/net/team/teamcore.c:2929 notifiercallchain+0x19d/0x3a0 kernel/notifier.c:85 callnetdevicenotifiersextack net/core/dev.c:2281 [inline] callnetdevicenotifiers net/core/dev.c:2295 [inline] devchangenetnamespace+0xcb7/0x2050 net/core/dev.c:12592 dosetlink+0x2ce/0x4590 net/core/rtnetlink.c:3060 rtnlchangelink net/core/rtnetlink.c:3776 [inline] rtnlnewlink net/core/rtnetlink.c:3935 [inline] rtnlnewlink+0x15a9/0x1be0 net/core/rtnetlink.c:4072 rtnetlinkrcvmsg+0x7d5/0xbe0 net/core/rtnetlink.c:6958 netlinkrcvskb+0x232/0x4b0 net/netlink/afnetlink.c:2550 netlinkunicastkernel net/netlink/afnetlink.c:1318 [inline] netlinkunicast+0x80f/0x9b0 net/netlink/afnetlink.c:1344 netlinksendmsg+0x813/0xb40 net/netlink/afnetlink.c:1894
problem. Ido Schimmel found steps to reproduce
ip link add name team1 type team ip link add name dummy1 mtu 1499 master team1 type dummy ip netns add ns1 ip link set dev dummy1 netns ns1 ip -n ns1 link del dev dummy1
and also found that the same issue was fixed in the bond driver in commit f51048c3e07b ("bonding: avoid NETDEVCHANGEMTU event when unregistering slave").
Let's do similar thing for the team driver, with commit ad7c7b2172c3 ("net: hold netdev instance lock during sysfs operations") and commit 303a8487a657 ("net: s/devsetmtu/netifsetmtu/") also applied.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.16 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.19.6 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.19.6-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch ad7c7b2172c3 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch 303a8487a657
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43234?
CVE-2026-43234 has a moderate severity level impacting the Linux kernel.
How do I fix CVE-2026-43234?
To mitigate CVE-2026-43234, you should update to the latest stable version of the Linux kernel where the vulnerability is patched.
Which versions of the Linux kernel are affected by CVE-2026-43234?
CVE-2026-43234 affects specific versions of the Linux kernel prior to the implemented fix.
Is CVE-2026-43234 exploitable remotely?
CVE-2026-43234 is not considered a remote code execution vulnerability, but can impact local operations.
What does CVE-2026-43234 involve regarding network device events?
CVE-2026-43234 involves avoiding NETDEV_CHANGEMTU events when unregistering slave network devices.