CVE-2026-31678

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

openvswitch: defer tunnel netdev_put to RCU release

ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe vport->dev.

Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let vport_netdev_free() drop the reference from the RCU callback, matching the non-tunnel destroy path and avoiding additional synchronization under RTNL.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

April 25, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

openvswitch: defer tunnel netdev_put to RCU release - kernel/git/stable/linux.git - Linux kernel stable tree

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

openvswitch: defer tunnel netdev_put to RCU release - kernel/git/stable/linux.git - Linux kernel stable tree

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

openvswitch: defer tunnel netdev_put to RCU release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d56aced21fb9c104e8a3f3be9b21fbafe448ffc
generic

openvswitch: defer tunnel netdev_put to RCU release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98b726ab5e2a4811e27c28e4d041f75bba147eab
generic

openvswitch: defer tunnel netdev_put to RCU release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6931d21f87bc6d657f145798fad0bf077b82486c
generic

openvswitch: defer tunnel netdev_put to RCU release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42f0d3d81209654c08ffdde5a34b9b92d2645896

Vendor Advisories for CVE-2026-31678(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.168osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 5× in last 7d / 26× 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 241 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31678?
CVE-2026-31678 is a high vulnerability published on April 25, 2026. In the Linux kernel, the following vulnerability has been resolved: openvswitch: defer tunnel netdev_put to RCU release ovsnetdevtunneldestroy() may run after NETDEVUNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe…
When was CVE-2026-31678 disclosed?
CVE-2026-31678 was first published in the National Vulnerability Database on April 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31678 actively exploited?
CVE-2026-31678 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31678?
CVE-2026-31678 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31678?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31678, 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-31678

Explore →

Is Your Infrastructure Affected by CVE-2026-31678?

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