IT

Tracker / CVE-2026-46165

CVE-2026-46165

Medium 5.5

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 products and versions

linux linux_kernel
linux linux_kernel · 6.1.168 → 6.1.175
linux linux_kernel · 6.12.80 → 6.12.88
linux linux_kernel · 6.18.21 → 6.18.30
linux linux_kernel · 6.19.11 → 7.0
linux linux_kernel · 6.6.131 → 6.6.140
linux linux_kernel · 7.0.1 → 7.0.7

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References