CVE-2026-46165 Details
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.
A self-deadlock vulnerability has been identified in the Open vSwitch component of the Linux kernel, specifically within the vport handling of tunnel ports. This issue arises because vports are used concurrently and are protected by Read-Copy-Update (RCU) mechanisms. The function netdev_put() must be called after the RCU grace period, either within an RCU call or following a synchronize_net() call. However, the rtnl_delete_link() function, which is necessary for deleting network devices, must be executed under the Real-Time Netlink (RTNL) context and cannot be performed in RCU context. The current implementation leads to a deadlock during device removal, as the vport is not freed and the reference is not released, causing a blockage until all references are cleared. This vulnerability affects several versions of the Linux kernel.
The vulnerability has been fixed by adjusting the order of operations in the vport destruction process. The RCU callback is now scheduled before releasing the RTNL lock, allowing the vport to be properly freed and the references released without causing a deadlock.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/366c482965c673565ecb8bcfb15d5548f13a6a10 | kernel.org | Patch |
| https://git.kernel.org/stable/c/3df75fff46b1517eb479d8e6b8e3500763715dd0 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6522d59fb7de55ce0f0f285d962243ddffebb01f | kernel.org | Patch |
| https://git.kernel.org/stable/c/8ae6c15fc473c9ad03b0173330cce9a092c76154 | kernel.org | Patch |
| https://git.kernel.org/stable/c/aa69918bd418e700309fdd08509dba324fb24296 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c741433f6c8dcdecd1d9549d89053761fd1ea413 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.1.168, < 6.1.175 >= 6.6.131, < 6.6.140 >= 6.12.80, < 6.12.88 >= 6.18.21, < 6.18.30 >= 6.19.11, < 7.0 >= 7.0.1, < 7.0.7 7.0 - 7.0 rc6 7.0 rc7 7.1 rc1 7.1 rc2 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 10, 2026 | Initial Analysis | [email protected] |
| Jun 1, 2026 | CVE Modified | kernel.org |
| May 28, 2026 | New CVE Received | kernel.org |