net: avoid race between device unregistration and ethnl ops
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.179, 5.11, 6.1.129, 6.6.76, 6.12.13, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: net: avoid race between device unregistration and ethnl ops The following trace can be seen if a device is being unregistered while its number of channels are being modified. DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 3 PID: 3754 at kernel/locking/mutex.c:564 __mutex_lock+0xc8a/0x1120 CPU: 3 UID: 0 PID: 3754 Comm: ethtool Not tainted 6.13.0-rc6+ #771 RIP: 0010:__mutex_lock+0xc8a/0x1120 Call Trace: <TASK> ethtool_check_max_channel+0x1ea/0x880 ethnl_set_channels+0x3c3/0xb10 ethnl_default_set_doit+0x306/0x650 genl_family_rcv_msg_doit+0x1e3/0x2c0 genl_rcv_msg+0x432/0x6f0 netlink_rcv_skb+0x13d/0x3b0 genl_rcv+0x28/0x40 netlink_unicast+0x42e/0x720 netlink_sendmsg+0x765/0xc20 __sys_sendto+0x3ac/0x420 __x64_sys_sendto+0xe0/0x1c0 do_syscall_64+0x95/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e This is because unregister_netdevice_many_notify might run before the rtnl lock section of ethnl operations, eg. set_channels in the above example. In this example the rss lock would be destroyed by the device unregistration path before being used again, but in general running ethnl operations while dismantle has started is not a good idea. Fix this by denying any operation on devices being unregistered. A check was already there in ethnl_ops_begin, but not wide enough. Note that the same issue cannot be seen on the ioctl version (__dev_ethtool) because the device reference is retrieved from within the rtnl lock section there. Once dismantle started, the net device is unlisted and no reference will be found.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From cfd719f04267108f5f5bf802b9d7de69e99a99f9 · fixed in 26bc6076798aa4dc83a07d0a386f9e57c94e8517; From dde91ccfa25fd58f64c397d91b81a4b393100ffa · fixed in b1cb37a31a482df3dd35a6ac166282dac47664f4; From dde91ccfa25fd58f64c397d91b81a4b393100ffa · fixed in 2f29127e94ae9fdc7497331003d6860e9551cdf3; From dde91ccfa25fd58f64c397d91b81a4b393100ffa · fixed in b382ab9b885cbb665e0e70a727f101c981b4edf3; From dde91ccfa25fd58f64c397d91b81a4b393100ffa · fixed in 4dc880245f9b529fa8f476b5553c799d2848b47b; From dde91ccfa25fd58f64c397d91b81a4b393100ffa · fixed in 12e070eb6964b341b41677fd260af5a305316a1f; From 5.15.8 · fixed in 5.15.179; From 5.10.87 · fixed in 5.11
- Linux Linux
5.16
- KernelLinux
fixed in 5.15.179; From 5.16.0 · fixed in 6.1.129; fixed in 6.6.76; From 6.2.0 · fixed in 6.12.13; From 6.7.0 · fixed in 6.13.2
- :linux_kernel:Android
From :0 · fixed in :2025-09-05