ovpn: fix race between deleting interface and adding new peer
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.18.347.0.117.1In the Linux kernel, the following vulnerability has been resolved:
ovpn: fix race between deleting interface and adding new peer
While deleting an existing ovpn interface, there is a very narrow window where adding a new peer via netlink may cause the netdevice to hang and prevent its unregistration.
It may happen during ovpn_dellink(), when all existing peers are freed and the device is queued for deregistration, but a CMD_PEER_NEW message comes in adding a new peer that takes again a reference to the netdev.
At this point there is no way to release the device because we are under the assumption that all peers were already released.
Fix the race condition by releasing all peers in ndo_uninit(), when the netdevice has already been removed from the netdev list.
Also ovpn_peer_add() has now an extra check that forces the function to bail out if the device reg_state is not REGISTERED. This way any incoming CMD_PEER_NEW racing with the interface deletion routine will simply stop before adding the peer.
Note that the above check happens while holding the netdev_lock to prevent racing netdev state changes.
From the CVE record · Linux
A race in the Linux kernel’s ovpn component can occur when a new peer is added via netlink while an ovpn interface is being deleted. An actor able to send the peer-add message during that narrow window can cause the network device to hang and prevent its unregistration. The input does not specify authentication requirements or user interaction.
Engineers running Linux kernels with the ovpn component should check their kernel versions; affected versions are not specified.