cbcvebase.
CVE-2025-21701
published 2025-02-13

CVE-2025-21701: 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…

PriorityP416medium4.7CVSS 3.1
AVLACHPRLUINSUCNINAH
EPSS
0.17%
6.4th percentile
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: 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.

Affected

29 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.129-1 (bookworm)linux 6.1.129-1 (bookworm)
debianlinux-6.1< linux 6.1.129-1 (bookworm)linux 6.1.129-1 (bookworm)
googlechrome_chrome
linuxlinux
linuxlinux
linuxlinux>= 5.10.87 < 5.115.11
linuxlinux>= 5.15.8 < 5.15.1795.15.179
linuxlinux>= cfd719f04267108f5f5bf802b9d7de69e99a99f9 < 26bc6076798aa4dc83a07d0a386f9e57c94e851726bc6076798aa4dc83a07d0a386f9e57c94e8517
linuxlinux>= dde91ccfa25fd58f64c397d91b81a4b393100ffa < b1cb37a31a482df3dd35a6ac166282dac47664f4b1cb37a31a482df3dd35a6ac166282dac47664f4
linuxlinux>= dde91ccfa25fd58f64c397d91b81a4b393100ffa < 2f29127e94ae9fdc7497331003d6860e9551cdf32f29127e94ae9fdc7497331003d6860e9551cdf3
linuxlinux>= dde91ccfa25fd58f64c397d91b81a4b393100ffa < b382ab9b885cbb665e0e70a727f101c981b4edf3b382ab9b885cbb665e0e70a727f101c981b4edf3
linuxlinux>= dde91ccfa25fd58f64c397d91b81a4b393100ffa < 4dc880245f9b529fa8f476b5553c799d2848b47b4dc880245f9b529fa8f476b5553c799d2848b47b
linuxlinux>= dde91ccfa25fd58f64c397d91b81a4b393100ffa < 12e070eb6964b341b41677fd260af5a305316a1f12e070eb6964b341b41677fd260af5a305316a1f
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 6.1.129-16.1.129-1
linuxlinux_kernel>= 0 < 6.12.13-16.12.13-1
linuxlinux_kernel>= 0 < 6.12.13-16.12.13-1
linuxlinux_kernel>= 0 < 5.15.0-138.1485.15.0-138.148
linuxlinux_kernel>= 0 < 6.8.0-58.606.8.0-58.60
linuxlinux_kernel>= 5.10.87 < 5.115.11
linuxlinux_kernel>= 5.15.8 < 5.15.1795.15.179

CVSS provenance

nvdv3.14.7MEDIUMCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian4.7MEDIUM
vendor_redhat4.7MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.