Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3600033f31b1afa16d73a24905eec9ee1d222b97, 366c482965c673565ecb8bcfb15d5548f13a6a10, 3df75fff46b1517eb479d8e6b8e3500763715dd0; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 3600033f31b1afa16d73a24905eec9ee1d222b97, 366c482965c673565ecb8bcfb15d5548f13a6a10, 3df75fff46b1517eb479d8e6b8e3500763715dd0; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 28, 2026
Updated
Nov 6, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46165

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.1.168 and later · before 6.1.175
  • linux linux kernel6.6.131 and later · before 6.6.140
  • linux linux kernel6.12.80 and later · before 6.12.88
  • linux linux kernel6.18.21 and later · before 6.18.30
  • linux linux kernel6.19.11 and later · before 7.0
  • linux linux kernel7.0.1 and later · before 7.0.7
  • linux linux kernel7.0
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • b8c56a3fc5d879c0928f207a756b0f067f06c6a8, 7.0affected
    • f0ec49d3a39c1f5a4f3270ea27ca0854fad2a2a2 and later · before 3600033f31b1afa16d73a24905eec9ee1d222b97affected · git
    • 9d56aced21fb9c104e8a3f3be9b21fbafe448ffc and later · before 8ae6c15fc473c9ad03b0173330cce9a092c76154affected · git
    • 42f0d3d81209654c08ffdde5a34b9b92d2645896 and later · before c741433f6c8dcdecd1d9549d89053761fd1ea413affected · git
    • bbe7bd722bfaea36aab3da6cc60fb4a05c644643 and later · before 6522d59fb7de55ce0f0f285d962243ddffebb01faffected · git
    • 98b726ab5e2a4811e27c28e4d041f75bba147eab and later · before 3df75fff46b1517eb479d8e6b8e3500763715dd0affected · git
    • 6931d21f87bc6d657f145798fad0bf077b82486c and later · before 366c482965c673565ecb8bcfb15d5548f13a6a10affected · git
    • 6931d21f87bc6d657f145798fad0bf077b82486c and later · before aa69918bd418e700309fdd08509dba324fb24296affected · git
    • 6.1.168 and later · before 6.1.175affected · semver
    • 6.6.131 and later · before 6.6.140affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.88-16.12.88-1
Debian:14linuxbefore 7.0.7-17.0.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46162May 28, 2026 · ice: fix double free in ice_sf_eth_activate() error path
    31Monitor
  • ← EarlierCVE-2026-46163May 28, 2026 · wifi: b43legacy: enforce bounds check on firmware key index in RX path
    31Monitor
  • Later →CVE-2026-46166May 28, 2026 · wifi: mac80211: use safe list iteration in radar detect work
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3600033f31b1afa16d73a24905eec9ee1d222b97Vendor (CNA)
Linux Linux366c482965c673565ecb8bcfb15d5548f13a6a10Vendor (CNA)
Linux Linux3df75fff46b1517eb479d8e6b8e3500763715dd0Vendor (CNA)
Linux Linux6.1.175Vendor (CNA)
Linux Linux6.12.88Vendor (CNA)
Linux Linux6.18.30Vendor (CNA)
Linux Linux6.20Vendor (CNA)
Linux Linux6.6.140Vendor (CNA)
Linux Linux6522d59fb7de55ce0f0f285d962243ddffebb01fVendor (CNA)
Linux Linux8ae6c15fc473c9ad03b0173330cce9a092c76154Vendor (CNA)
Linux Linuxaa69918bd418e700309fdd08509dba324fb24296Vendor (CNA)
Linux Linuxc741433f6c8dcdecd1d9549d89053761fd1ea413Vendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.141.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records