openvswitch: defer tunnel netdev_put to RCU release
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a9020fde67a6eb77f8130feff633189f99264db1 · < b8c56a3fc5d879c0928f207a756b0f067f06c6a8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
openvswitch: defer tunnel netdev_put to RCU release
ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe vport->dev.
Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let vport_netdev_free() drop the reference from the RCU callback, matching the non-tunnel destroy path and avoiding additional synchronization under RTNL.
From the CVE record · Linux
In the Linux kernel's openvswitch code, tunnel device destruction can release a device reference while concurrent readers still access it. This race could affect those readers; the input does not specify an attacker action, access requirement, or user interaction needed to trigger it.
Engineers running Linux kernels with openvswitch should check their systems; affected versions are not specified.