CVE-2026-97956: net: net_failover: Fix the deadlock in net_failover_slave_name_change()
In the Linux kernel, the following vulnerability has been resolved:
net: netfailover: Fix the deadlock in netfailoverslavenamechange()
This is a sibling fix of commit b84c5632c7b3 ("net: netfailover: Fix the deadlock in slave register"). There is netdevlockops() in the upper callers, so using netifopen() instead of devopen().
Call Trace: schedule+0x2bb/0x650 schedule+0x27/0xb0 schedulepreemptdisabled+0x15/0x30 mutexlock.constprop.0+0x550/0xaf0 mutexlockslowpath+0x13/0x20 mutexlock+0x3b/0x50 devopen+0x3b/0xe0 netfailoverslavenamechange+0x22/0x40 failoverevent+0xd4/0x1e0 notifiercallchain+0x62/0xf0 rawnotifiercallchain+0x16/0x30 callnetdevicenotifiersinfo+0x50/0x80 netifchangename+0x200/0x330 dosetlink.isra.0+0xb12/0xdf0 ? securitycapable+0x9a/0x1e0 ? nscapable+0x31/0x60 rtnlsetlink+0x302/0x670 ? netlinkrecvmsg+0x296/0x340 ? securitycapable+0x9a/0x1e0 ? pfxrtnlsetlink+0x10/0x10 rtnetlinkrcvmsg+0x384/0x460 ? pfxrtnetlinkrcvmsg+0x10/0x10 netlinkrcvskb+0x61/0x120 rtnetlinkrcv+0x15/0x30 netlinkunicast+0x28f/0x3c0 netlinksendmsg+0x216/0x450 syssendto+0x222/0x230 x64syssendto+0x24/0x40 x64syscall+0x1d5d/0x2390 dosyscall64+0x105/0x5a0 ? dosyscall64+0x140/0x5a0 ? excpagefault+0x94/0x1e0 entrySYSCALL64afterhwframe+0x76/0x7e
Affected Software
Event History
Frequently Asked Questions
What action reaches the affected code path?
The supplied call trace shows the path is reached while changing a network device name through rtnetlink, leading through netif_change_name() to net_failover_slave_name_change().
What is the observable impact if the issue is present?
The affected path can deadlock while dev_open() attempts to acquire a mutex that is already protected by netdev_lock_ops() in an upper caller. A blocked task stack can include net_failover_slave_name_change(), failover_event(), netif_change_name(), and rtnl_setlink().