Skip to main content
VulnerabilityPublished Updated

CVE-2026-46165: Linux kernel · openvswitch: vport: fix self-deadlock on release of tunnel ports

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-46165· High

Not known to be exploited · CVSS 5.5 High · fixed in c741433f6c8dcdecd1d9549d89053761fd1ea413 : patch Linux kernel soon.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
5.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
Patch
Available – fixed in c741433f6c8dcdecd1d9549d89053761fd1ea413, aa69918bd418e700309fdd08509dba324fb24296, 3600033f31b1afa16d73a24905eec9ee1d222b97 +9
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=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 <6.20
Fixed in
  • c741433f6c8dcdecd1d9549d89053761fd1ea413
  • aa69918bd418e700309fdd08509dba324fb24296
  • 3600033f31b1afa16d73a24905eec9ee1d222b97
  • 6522d59fb7de55ce0f0f285d962243ddffebb01f
  • 366c482965c673565ecb8bcfb15d5548f13a6a10
  • 8ae6c15fc473c9ad03b0173330cce9a092c76154
  • 6.20
  • 6.18.30
  • 6.12.88
  • 6.6.140
  • 6.1.175
  • 3df75fff46b1517eb479d8e6b8e3500763715dd0
LinuxLinuxAffected
  • =7.0
Fixed in–
Linuxlinux/kernelpkg:deb/linux/kernelOther threatsAffected
  • >=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 <6.20
  • =7.0
Fixed in
  • 6.1.175
  • 6.6.140
  • 6.12.88
  • 6.18.30
  • 6.20

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…