CVE-2026-97611

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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

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

net: openvswitch: fix use-after-free of the flow table mask array

tbl_mask_array_realloc() retires the old mask_array before it stops being reachable:

old = ovsl_dereference(tbl->mask_array); if (old) { ... call_rcu(&old->rcu, mask_array_rcu_cb); }

rcu_assign_pointer(tbl->mask_array, new);

call_rcu() only waits for read-side critical sections already in flight. tbl->mask_array still points at old between the call_rcu() and the rcu_assign_pointer(), so a reader entering ovs_flow_tbl_lookup_stats() in that window picks up old in a fresh critical section that the pending grace period does not cover.

tbl_mask_array_realloc() runs in process context under ovs_mutex, so the window is preemptible and can outlast the grace period. Then mask_array_rcu_cb() frees old before the swap runs:

BUG: KASAN: slab-use-after-free in flow_lookup.constprop.0+0x2bf/0x2f0 Read of size 8 at addr ffff888020b3e018 by task poc/741 flow_lookup.constprop.0+0x2bf/0x2f0 ovs_flow_tbl_lookup_stats+0x4a3/0x5c0 ovs_dp_process_packet+0x19c/0x710 ovs_vport_receive+0x243/0x390 internal_dev_xmit+0x81/0x170 Freed by task 728: kfree+0x16a/0x4e0 rcu_core+0x853/0x1030

Publish the new array before retiring the old one. The kfree_rcu() that call_rcu() replaced ran after the swap.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

October 3, 2026

Advisory Details (4)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

net: openvswitch: fix use-after-free of the flow table mask array - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: fix use-after-free of the flow table mask array - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/035e9c3722067648a99010711d0ce81f42572ef4
generic

net: openvswitch: fix use-after-free of the flow table mask array - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: fix use-after-free of the flow table mask array - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cd982e11684def5d4a9fcfd5354de09032828414

Vendor Advisories for CVE-2026-97611(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 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 44× in last 7d / 64× 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.

  1. 2026-10-05 08:01 UTCEG score recompute
  2. 2026-10-05 08:01 UTCVendor advisory
  3. 2026-10-05 08:01 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 20:52 UTCVendor advisory
  6. 2026-10-04 20:52 UTCGHSA enrichment
  7. 2026-10-04 09:43 UTCVendor advisory
  8. 2026-10-04 09:43 UTCGHSA enrichment
  9. 2026-10-03 22:32 UTCEG score recompute
  10. 2026-10-03 22:32 UTCVendor advisory
  11. 2026-10-03 22:32 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 11:23 UTCEG score recompute
  14. 2026-10-03 11:23 UTCVendor advisory
  15. 2026-10-03 11:22 UTCGHSA enrichment
  16. 2026-10-03 02:36 UTCEG score recompute
  17. 2026-10-03 02:36 UTCVendor advisory
  18. 2026-10-03 02:36 UTCGHSA enrichment
  19. 2026-10-02 17:57 UTCEPSS rescore
  20. 2026-10-02 15:27 UTCVendor advisory
  21. 2026-10-02 15:27 UTCGHSA enrichment
  22. 2026-10-02 04:17 UTCEG score recompute
  23. 2026-10-02 04:17 UTCVendor advisory
  24. 2026-10-02 04:16 UTCGHSA enrichment
  25. 2026-10-01 19:51 UTCEPSS rescore
Show 39 more
  1. 2026-10-01 17:01 UTCVendor advisory
  2. 2026-10-01 17:01 UTCGHSA enrichment
  3. 2026-10-01 05:30 UTCVendor advisory
  4. 2026-10-01 05:30 UTCGHSA enrichment
  5. 2026-09-30 18:21 UTCEG score recompute
  6. 2026-09-30 18:21 UTCGHSA enrichment
  7. 2026-09-30 15:04 UTCEPSS rescore
  8. 2026-09-30 07:12 UTCVendor advisory
  9. 2026-09-30 07:12 UTCGHSA enrichment
  10. 2026-09-29 20:03 UTCEG score recompute
  11. 2026-09-29 20:03 UTCVendor advisory
  12. 2026-09-29 20:03 UTCGHSA enrichment
  13. 2026-09-29 08:53 UTCVendor advisory
  14. 2026-09-29 08:53 UTCGHSA enrichment
  15. 2026-09-28 21:44 UTCEG score recompute
  16. 2026-09-28 21:44 UTCVendor advisory
  17. 2026-09-28 21:44 UTCGHSA enrichment
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 10:35 UTCVendor advisory
  21. 2026-09-28 10:34 UTCGHSA enrichment
  22. 2026-09-27 23:22 UTCEG score recompute
  23. 2026-09-27 23:22 UTCGHSA enrichment
  24. 2026-09-27 13:49 UTCEPSS rescore
  25. 2026-09-27 12:13 UTCGHSA enrichment
  26. 2026-09-27 01:03 UTCEG score recompute
  27. 2026-09-27 01:03 UTCGHSA enrichment
  28. 2026-09-26 15:59 UTCEPSS rescore
  29. 2026-09-26 13:54 UTCGHSA enrichment
  30. 2026-09-26 02:37 UTCEG score recompute
  31. 2026-09-26 02:37 UTCGHSA enrichment
  32. 2026-09-25 15:24 UTCEG score recompute
  33. 2026-09-25 15:24 UTCGHSA enrichment
  34. 2026-09-25 14:52 UTCEG score recompute▲ 7.80
  35. 2026-09-25 14:52 UTCGHSA enrichment
  36. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  37. 2026-09-25 11:30 UTCNVD update
  38. 2026-09-25 10:38 UTCEG score recompute
  39. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97611?
CVE-2026-97611 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix use-after-free of the flow table mask array tblmaskarrayrealloc() retires the old maskarray before it stops being reachable: old = ovsldereference(tbl->maskarray); if (old) { ... callrcu(&old->rcu,…
When was CVE-2026-97611 disclosed?
CVE-2026-97611 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97611 actively exploited?
CVE-2026-97611 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97611?
CVE-2026-97611 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-97611?
No fix for CVE-2026-97611 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97611 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-97611

Explore →

Is Your Infrastructure Affected by CVE-2026-97611?

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

Book a Demo →Browse All CVEs