CVE-2026-46165

published 28 May 2026 · updated 19 Nov 2026

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

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.1.175, Kernel 6.12.88, Kernel 6.18.30 and 11 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=6.1.168 <6.1.175, >=6.12.80 <6.12.88, >=6.18.21 <6.18.30, >=6.19.11 <7.0, >=6.6.131 <6.6.140, >=7.0.1 <7.0.7, =7.0, =7.1, >=6931d21f87bc6d657f145798fad0bf077b82486c <366c482965c673565ecb8bcfb15d5548f13a6a10, >=6931d21f87bc6d657f145798fad0bf077b82486c <aa69918bd418e700309fdd08509dba324fb24296, >=98b726ab5e2a4811e27c28e4d041f75bba147eab <3df75fff46b1517eb479d8e6b8e3500763715dd0, >=9d56aced21fb9c104e8a3f3be9b21fbafe448ffc <8ae6c15fc473c9ad03b0173330cce9a092c76154, >=bbe7bd722bfaea36aab3da6cc60fb4a05c644643 <6522d59fb7de55ce0f0f285d962243ddffebb01f, >=f0ec49d3a39c1f5a4f3270ea27ca0854fad2a2a2 <3600033f31b1afa16d73a24905eec9ee1d222b97, =b8c56a3fc5d879c0928f207a756b0f067f06c6a8, >=42f0d3d81209654c08ffdde5a34b9b92d2645896 <c741433f6c8dcdecd1d9549d89053761fd1ea413, >=6.19.11 <6.206.1.175, 6.12.88, 6.18.30, 7.0, 6.6.140, 7.0.7, 366c482965c673565ecb8bcfb15d5548f13a6a10, aa69918bd418e700309fdd08509dba324fb24296, 3df75fff46b1517eb479d8e6b8e3500763715dd0, 8ae6c15fc473c9ad03b0173330cce9a092c76154, 6522d59fb7de55ce0f0f285d962243ddffebb01f, 3600033f31b1afa16d73a24905eec9ee1d222b97, c741433f6c8dcdecd1d9549d89053761fd1ea413, 6.20
linux-kernel: Kernel>=6.1.168 <6.1.175, >=6.12.80 <6.12.88, >=6.18.21 <6.18.30, >=6.19.11 <6.20, >=6.6.131 <6.6.140, >=7.0.0 <7.0.76.1.175, 6.12.88, 6.18.30, 6.20, 6.6.140, 7.0.7

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-46165 severity on Zeptric[![CVE-2026-46165](https://zeptric.io/badge/cve/CVE-2026-46165.svg)](https://zeptric.io/cve/CVE-2026-46165)