virtio-net: fix recursived rtnl_lock() during probe()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
6.12
|
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().
From the CVE record · Linux
The Linux kernel’s virtio-net driver can deadlock during device probing when the VMM sends a VIRTIO_NET_S_ANNOUNCE request. The input does not specify whether an attacker can trigger this or what access they would need.
Engineers running Linux kernels with the virtio-net driver should check their versions; affected versions are not specified.