Linux Kernel up to 7.1-rc2 openvswitch netdev_put deadlock

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.0$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.6.139/6.12.87/6.18.29/7.0.6/7.1-rc2. This vulnerability affects the function netdev_put of the component openvswitch. Executing a manipulation can lead to deadlock. This vulnerability appears as CVE-2026-46165. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.6.139/6.12.87/6.18.29/7.0.6/7.1-rc2. This vulnerability affects the function netdev_put of the component openvswitch. The manipulation with an unknown input leads to a deadlock vulnerability. The CWE definition for the vulnerability is CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. As an impact it is known to affect availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-46165 since 05/13/2026. The exploitation appears to be difficult. There are known technical details, but no exploit is available.

Upgrading to version 6.6.140, 6.12.88, 6.18.30, 7.0.7 or 7.1-rc3 eliminates this vulnerability. Applying the patch c741433f6c8dcdecd1d9549d89053761fd1ea413/6522d59fb7de55ce0f0f285d962243ddffebb01f/3df75fff46b1517eb479d8e6b8e3500763715dd0/366c482965c673565ecb8bcfb15d5548f13a6a10/aa69918bd418e700309fdd08509dba324fb24296 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.1
VulDB Meta Temp Score: 5.0

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Deadlock
CWE: CWE-833 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.140/6.12.88/6.18.30/7.0.7/7.1-rc3
Patch: c741433f6c8dcdecd1d9549d89053761fd1ea413/6522d59fb7de55ce0f0f285d962243ddffebb01f/3df75fff46b1517eb479d8e6b8e3500763715dd0/366c482965c673565ecb8bcfb15d5548f13a6a10/aa69918bd418e700309fdd08509dba324fb24296

Timelineinfo

05/13/2026 CVE reserved
05/28/2026 +15 days Advisory disclosed
05/28/2026 +0 days VulDB entry created
06/11/2026 +13 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46165 (🔒)
GCVE (CVE): GCVE-0-2026-46165
GCVE (VulDB): GCVE-100-366688

Entryinfo

Created: 05/28/2026 13:38
Updated: 06/11/2026 00:03
Changes: 05/28/2026 13:38 (59), 06/11/2026 00:03 (11)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!