CVE-2026-46165openvswitch: vport: fix self-deadlock on release of tunnel ports

Official description

In the Linux kernel, the following vulnerability has been resolved: openvswitch: vport: fix self-deadlock on release of tunnel ports vports are used concurrently and protected by RCU, so netdev_put() must happen after the RCU grace period. So, either in an RCU call or after the synchronize_net(). The rtnl_delete_link() must happen under RTNL and so can't be executed in RCU context. Calling synchronize_net() while holding RTNL is not a good idea for performance and system stability under load in general, so calling netdev_put() in RCU call is the right solution here. However, when the device is deleted, rtnl_unlock() will call netdev_run_todo() and block until all the references are gone. In the current code this means that we never reach the call_rcu() and the vport is never freed and the reference is never released, causing a self-deadlock on device removal. Fix that by moving the rcu_call() before the rtnl_unlock(), so the scheduled RCU callback will be executed when synchronize_net() is called from the rtnl_unlock()->netdev_run_todo() while the RTNL itself is already released.

Affected packages & fixed versions

Affected products (as reported)

References

• https://git.kernel.org/stable/c/3600033f31b1afa16d73a24905eec9ee1d222b97
• https://git.kernel.org/stable/c/8ae6c15fc473c9ad03b0173330cce9a092c76154
• https://git.kernel.org/stable/c/c741433f6c8dcdecd1d9549d89053761fd1ea413
• https://git.kernel.org/stable/c/6522d59fb7de55ce0f0f285d962243ddffebb01f
• https://git.kernel.org/stable/c/3df75fff46b1517eb479d8e6b8e3500763715dd0
• https://git.kernel.org/stable/c/366c482965c673565ecb8bcfb15d5548f13a6a10
• https://git.kernel.org/stable/c/aa69918bd418e700309fdd08509dba324fb24296
• https://cert-portal.siemens.com/productcert/html/ssa-784472.html