Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-46165

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 6.1.175, 6.6.140, 6.12.88, 6.18.30, 6.20, and 1 more
None on Exploit-DB, Metasploit or GitHub

Summary

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.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 6.1.168 · fixed in 6.1.175; From 6.6.131 · fixed in 6.6.140; From 6.12.80 · fixed in 6.12.88; From 6.18.21 · fixed in 6.18.30; From 6.19.11 · fixed in 6.20

  • Linux Linux

    7.0

  • KernelLinux

    fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.88; From 6.13.0 · fixed in 6.18.30; From 6.19.0 · fixed in 7.0.7

References 7

git.kernel.org