In the Linux kernel, the following vulnerability has been resolved:
virtio-net: fix recursived rtnl_lock() during probe()
The deadlock appears in a stack trace like:
virtnet_probe()
rtnl_lock()
virtio_config_changed_work()
netdev_notify_peers()
rtnl_lock()
It happens if the VMM sends a VIRTIO_NET_S_ANNOUNCE request while the
virtio-net driver is still probing.
The config_work in probe() will get scheduled until virtnet_open() enables
the config change notification via virtio_config_driver_enable().
Metrics
Affected Vendors & Products
References
History
Sat, 16 Aug 2025 11:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: virtio-net: fix recursived rtnl_lock() during probe() The deadlock appears in a stack trace like: virtnet_probe() rtnl_lock() virtio_config_changed_work() netdev_notify_peers() rtnl_lock() It happens if the VMM sends a VIRTIO_NET_S_ANNOUNCE request while the virtio-net driver is still probing. The config_work in probe() will get scheduled until virtnet_open() enables the config change notification via virtio_config_driver_enable(). | |
Title | virtio-net: fix recursived rtnl_lock() during probe() | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-08-16T11:34:19.544Z
Updated: 2025-08-16T11:34:19.544Z
Reserved: 2025-04-16T04:51:24.024Z
Link: CVE-2025-38551

No data.

Status : Received
Published: 2025-08-16T12:15:31.267
Modified: 2025-08-16T12:15:31.267
Link: CVE-2025-38551

No data.