CVE-2026-80994

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-11. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: openvswitch: fix flow mask use-after-free on flow deletion

The commit in the Fixes tag below made so flow->mask free is scheduled via RCU right after it is removed from the flow table. The pointer stays in the flow structure and it can be accessible while in the same RCU critical section. This is done to avoid requiring ovs_mutex for the ovs_flow_free().

However, while removing the flow during processing of CMD_DEL, we do not take RCU read lock before the removal, and ovs_flow_cmd_fill_info() uses the flow->mask pointer afterwards. The RCU read lock is taken, but it's already late at that point. The comment on that line acknowledges that the lock is cosmetic and doesn't serve a real purpose.

This leads to use-after-free if the RCU grace period passes between removal and the filling. It is a short race window, but it is there and can lead to a real crash in case memory allocation for the info takes a bit longer:

BUG: KASAN: slab-use-after-free in __ovs_nla_put_key net/openvswitch/flow_netlink.c:1996 BUG: KASAN: slab-use-after-free in ovs_nla_put_key+0x2463/0x2e30 net/openvswitch/flow_netlink.c:2250 Read of size 4 at addr ffff88801ee89970 by task ovs_flow_del_ec/9487

Call Trace: __ovs_nla_put_key net/openvswitch/flow_netlink.c:1996 ovs_nla_put_key+0x2463/0x2e30 net/openvswitch/flow_netlink.c:2250 ovs_flow_cmd_fill_info+0x420/0x9c0 net/openvswitch/datapath.c:930 ovs_flow_cmd_del+0x53a/0x970 net/openvswitch/datapath.c:1467 ... netlink_rcv_skb+0x156/0x420 net/netlink/af_netlink.c:2556

Allocated by task 9487: mask_alloc net/openvswitch/flow_table.c:967 flow_mask_insert net/openvswitch/flow_table.c:1012 ovs_flow_tbl_insert+0xea2/0x1a90 net/openvswitch/flow_table.c:1084 ovs_flow_cmd_new+0x7e3/0xd90 net/openvswitch/datapath.c:1086 ... netlink_rcv_skb+0x156/0x420 net/netlink/af_netlink.c:2556

Freed by task 9485: rcu_free_sheaf+0x1e/0x100 mm/slub.c:5978 rcu_do_batch kernel/rcu/tree.c:2645 rcu_core+0x59c/0x10c0 kernel/rcu/tree.c:2897 handle_softirqs+0x1e4/0x9a0 kernel/softirq.c:622 ... instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1062

ovs_flow_tbl_remove() must be called after the ovs_flow_cmd_fill_info() to avoid this race. This also helps with cleaning up the forced cast and the cosmetic RCU read lock. Before the commit in the Fixes tag the order did not matter as long as the flow object itself was not freed.

A wider RCU critical section could be another option, but we have a GFP_KERNEL allocation in the way.

Reported by Trend Micro's Zero Day Initiative as ZDI-CAN-32042.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 14, 2026

Advisory Details (4)

Auto-updated Sep 13, 2026
Patch available.
Web page

net: openvswitch: fix flow mask use-after-free on flow deletion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e30317ff67a2eb12b4d890d39f72fd7e7117d48
Web page

net: openvswitch: fix flow mask use-after-free on flow deletion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f072b84afd05a77963eb1872f7174e280661dce
Web page

net: openvswitch: fix flow mask use-after-free on flow deletion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ac73e3af571da06c1d1cfe3f0f00dc978b851700
Web page

net: openvswitch: fix flow mask use-after-free on flow deletion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ba5cbc2f049af94ec94ff6f64958545efc5eaa2

Vendor Advisories for CVE-2026-80994(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 36× in last 7d / 180× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 191 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-80994?
CVE-2026-80994 is a high-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix flow mask use-after-free on flow deletion The commit in the Fixes tag below made so flow->mask free is scheduled via RCU right after it is removed from the flow table. The pointer stays in the flow structure…
When was the CVE record for CVE-2026-80994 published?
The CVE record for CVE-2026-80994 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-80994 actively exploited?
CVE-2026-80994 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80994?
CVE-2026-80994 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80994?
A fix for CVE-2026-80994 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80994 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-80994?

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

Book a Demo →Browse All CVEs