CVE-2026-46165

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-05-28.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
—
EG Score
5.5(low)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 14, 2026

Advisory Details (6)

Auto-updated Jun 13, 2026
No patch confirmed yet.
generic

openvswitch: vport: fix self-deadlock on release of tunnel ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c741433f6c8dcdecd1d9549d89053761fd1ea413
generic

openvswitch: vport: fix self-deadlock on release of tunnel ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aa69918bd418e700309fdd08509dba324fb24296
generic

openvswitch: vport: fix self-deadlock on release of tunnel ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ae6c15fc473c9ad03b0173330cce9a092c76154
generic

openvswitch: vport: fix self-deadlock on release of tunnel ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6522d59fb7de55ce0f0f285d962243ddffebb01f
generic

openvswitch: vport: fix self-deadlock on release of tunnel ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3df75fff46b1517eb479d8e6b8e3500763715dd0
generic

openvswitch: vport: fix self-deadlock on release of tunnel ports - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/366c482965c673565ecb8bcfb15d5548f13a6a10

Vendor Advisories for CVE-2026-46165(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 3× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 194 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 04:53 UTCEG score recompute
  8. 2026-08-25 04:53 UTCVendor advisory
  9. 2026-08-25 04:53 UTCGHSA enrichment
  10. 2026-08-23 14:42 UTCEG score recompute
  11. 2026-08-23 14:42 UTCVendor advisory
  12. 2026-08-23 14:42 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 15:35 UTCEG score recompute
  15. 2026-08-21 15:35 UTCVendor advisory
  16. 2026-08-21 15:35 UTCGHSA enrichment
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 10:57 UTCEG score recompute
  19. 2026-08-20 10:57 UTCVendor advisory
  20. 2026-08-20 10:57 UTCGHSA enrichment
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 08:55 UTCEG score recompute
  24. 2026-08-17 08:55 UTCVendor advisory
  25. 2026-08-17 08:55 UTCGHSA enrichment
Show 75 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:37 UTCEG score recompute
  3. 2026-08-16 02:37 UTCVendor advisory
  4. 2026-08-16 02:36 UTCGHSA enrichment
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 23:56 UTCVendor advisory
  8. 2026-08-14 23:56 UTCGHSA enrichment
  9. 2026-08-14 01:15 UTCEG score recompute
  10. 2026-08-14 01:15 UTCVendor advisory
  11. 2026-08-14 01:15 UTCGHSA enrichment
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-12 21:32 UTCEG score recompute
  14. 2026-08-12 21:32 UTCVendor advisory
  15. 2026-08-12 21:32 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-11 22:52 UTCVendor advisory
  18. 2026-08-11 22:52 UTCGHSA enrichment
  19. 2026-08-11 00:07 UTCEG score recompute
  20. 2026-08-11 00:07 UTCVendor advisory
  21. 2026-08-11 00:07 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-09 17:17 UTCEG score recompute
  24. 2026-08-09 17:17 UTCVendor advisory
  25. 2026-08-09 17:17 UTCGHSA enrichment
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-08 18:37 UTCEG score recompute
  28. 2026-08-08 18:37 UTCVendor advisory
  29. 2026-08-08 18:37 UTCGHSA enrichment
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-07 18:09 UTCEG score recompute
  32. 2026-08-07 18:09 UTCVendor advisory
  33. 2026-08-07 18:09 UTCGHSA enrichment
  34. 2026-08-06 19:29 UTCEG score recompute
  35. 2026-08-06 19:29 UTCVendor advisory
  36. 2026-08-06 19:29 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-05 20:48 UTCEG score recompute
  39. 2026-08-05 20:48 UTCVendor advisory
  40. 2026-08-05 20:48 UTCGHSA enrichment
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-04 15:10 UTCEPSS rescore
  43. 2026-08-04 10:39 UTCEPSS rescore
  44. 2026-08-03 16:15 UTCVendor advisory
  45. 2026-08-03 16:15 UTCGHSA enrichment
  46. 2026-08-02 13:25 UTCEG score recompute
  47. 2026-08-02 13:25 UTCVendor advisory
  48. 2026-08-02 13:25 UTCGHSA enrichment
  49. 2026-08-02 02:27 UTCEPSS rescore
  50. 2026-08-01 14:44 UTCEG score recompute
  51. 2026-08-01 14:44 UTCVendor advisory
  52. 2026-08-01 14:44 UTCGHSA enrichment
  53. 2026-08-01 04:16 UTCEPSS rescore
  54. 2026-07-31 06:41 UTCEG score recompute
  55. 2026-07-31 06:41 UTCVendor advisory
  56. 2026-07-31 06:41 UTCGHSA enrichment
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 01:30 UTCEPSS rescore
  59. 2026-07-29 14:32 UTCEG score recompute
  60. 2026-07-29 14:32 UTCVendor advisory
  61. 2026-07-29 14:32 UTCGHSA enrichment
  62. 2026-07-28 15:36 UTCEPSS rescore
  63. 2026-07-27 14:13 UTCEPSS rescore
  64. 2026-07-27 09:46 UTCEG score recompute
  65. 2026-07-27 09:46 UTCVendor advisory
  66. 2026-07-27 09:46 UTCGHSA enrichment
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-24 14:17 UTCEPSS rescore
  69. 2026-07-23 14:18 UTCEPSS rescore
  70. 2026-07-23 03:16 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-20 17:08 UTCEPSS rescore
  73. 2026-07-19 14:31 UTCEPSS rescore
  74. 2026-07-16 17:03 UTCEPSS rescore
  75. 2026-07-16 10:21 UTCVendor advisory

Frequently asked(4)

What is CVE-2026-46165?
CVE-2026-46165 is a medium vulnerability published on May 28, 2026. 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 synchronizenet().…
When was CVE-2026-46165 disclosed?
CVE-2026-46165 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46165 actively exploited?
CVE-2026-46165 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.1% of all scored CVEs.
How do I remediate CVE-2026-46165?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46165, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46165

Explore →

Is Your Infrastructure Affected by CVE-2026-46165?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs