CVE-2026-97612

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: mpls: clear inner_protocol when the last label is popped

skb_mpls_push() records the pre-encapsulation network header once, gated on !skb->inner_protocol. skb_mpls_pop() never clears that record, so it outlives the encapsulation it describes.

Open vSwitch can then re-push MPLS onto a packet whose inner_network_header still points at the older, deeper offset: push a label, pop every label, recirculate (ovs_flow_key_update() re-derives key->eth.type and resets network_header, but leaves inner_*), then push again. ovs_fragment() trusts the record:

skb->network_header = skb->inner_network_header;

so skb_network_offset() goes negative. The bound check is signed:

if (skb_network_offset(skb) > MAX_L2_LEN)

a negative offset passes it, and prepare_frag() widens the value:

unsigned int hlen = skb_network_offset(skb); memcpy(&data->l2_data, skb->data, hlen);

which is a ~4GiB memcpy out of a 30-byte per-CPU buffer.

Reproduced on v7.3-rc1. RDX is the truncated length, (unsigned int)(-8):

BUG: unable to handle page fault for address: ffffe8ffffc16000 #PF: supervisor write access in kernel mode Oops: 0002 [#1] SMP KASAN NOPTI RIP: 0010:memcpy+0x8/0x20 RDX: 00000000fffffff8 RSI: ffff888105d732db RDI: ffffe8ffffc16000 prepare_frag+0x3df/0x4e0 ovs_fragment+0x589/0x7e0 do_output+0x4ce/0x5e0 do_execute_actions+0x55d2/0x7b30 ovs_execute_actions+0xea/0x450

Same root-cause shape as commit 975b5b067f52 ("ipv6: sr: restore network header before routing and forwarding"): a stale network header offset reaching a consumer that widens it. Here it originates in the MPLS push/pop path.

Clear inner_protocol once the packet is no longer MPLS, so a later push re-records the current header. net/sched/act_mpls.c is the only other skb_mpls_pop() caller and gets the same fix; sch_frag.c saves and restores inner_protocol around fragmentation in the same way OVS does.

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
5th
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: mpls: clear inner_protocol when the last label is popped - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78a86d75a70e1e227711c72865c59b1422d0a5ae
generic

net: mpls: clear inner_protocol when the last label is popped - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mpls: clear inner_protocol when the last label is popped - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mpls: clear inner_protocol when the last label is popped - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/011e17b5cae19b9f6a150923275e41c278de64f0

Vendor Advisories for CVE-2026-97612(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 48× in last 7d / 68× 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 06:55 UTCEG score recompute
  2. 2026-10-05 06:55 UTCVendor advisory
  3. 2026-10-05 06:55 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 20:01 UTCVendor advisory
  6. 2026-10-04 20:01 UTCGHSA enrichment
  7. 2026-10-04 09:07 UTCVendor advisory
  8. 2026-10-04 09:07 UTCGHSA enrichment
  9. 2026-10-03 22:14 UTCEG score recompute
  10. 2026-10-03 22:14 UTCVendor advisory
  11. 2026-10-03 22:13 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 11:20 UTCEG score recompute
  14. 2026-10-03 11:20 UTCVendor advisory
  15. 2026-10-03 11:20 UTCGHSA enrichment
  16. 2026-10-03 09:58 UTCVendor advisory
  17. 2026-10-03 09:58 UTCGHSA enrichment
  18. 2026-10-02 23:05 UTCEG score recompute
  19. 2026-10-02 23:05 UTCVendor advisory
  20. 2026-10-02 23:05 UTCGHSA enrichment
  21. 2026-10-02 17:57 UTCEPSS rescore
  22. 2026-10-02 12:10 UTCVendor advisory
  23. 2026-10-02 12:09 UTCGHSA enrichment
  24. 2026-10-02 01:15 UTCEG score recompute
  25. 2026-10-02 01:15 UTCVendor advisory
Show 43 more
  1. 2026-10-02 01:15 UTCGHSA enrichment
  2. 2026-10-01 19:51 UTCEPSS rescore
  3. 2026-10-01 14:22 UTCVendor advisory
  4. 2026-10-01 14:22 UTCGHSA enrichment
  5. 2026-10-01 03:28 UTCVendor advisory
  6. 2026-10-01 03:28 UTCGHSA enrichment
  7. 2026-09-30 16:35 UTCEG score recompute
  8. 2026-09-30 16:35 UTCVendor advisory
  9. 2026-09-30 16:35 UTCGHSA enrichment
  10. 2026-09-30 15:04 UTCEPSS rescore
  11. 2026-09-30 05:08 UTCVendor advisory
  12. 2026-09-30 05:08 UTCGHSA enrichment
  13. 2026-09-29 18:15 UTCEG score recompute
  14. 2026-09-29 18:15 UTCVendor advisory
  15. 2026-09-29 18:15 UTCGHSA enrichment
  16. 2026-09-29 06:38 UTCEG score recompute
  17. 2026-09-29 06:38 UTCVendor advisory
  18. 2026-09-29 06:38 UTCGHSA enrichment
  19. 2026-09-28 19:45 UTCEG score recompute
  20. 2026-09-28 19:45 UTCVendor advisory
  21. 2026-09-28 19:44 UTCGHSA enrichment
  22. 2026-09-28 13:52 UTCEPSS rescore
  23. 2026-09-28 13:52 UTCEPSS rescore
  24. 2026-09-28 08:49 UTCVendor advisory
  25. 2026-09-28 08:49 UTCGHSA enrichment
  26. 2026-09-27 21:56 UTCEG score recompute
  27. 2026-09-27 21:55 UTCGHSA enrichment
  28. 2026-09-27 13:49 UTCEPSS rescore
  29. 2026-09-27 11:02 UTCGHSA enrichment
  30. 2026-09-27 00:10 UTCEG score recompute
  31. 2026-09-27 00:09 UTCGHSA enrichment
  32. 2026-09-26 15:59 UTCEPSS rescore
  33. 2026-09-26 13:14 UTCGHSA enrichment
  34. 2026-09-26 02:20 UTCEG score recompute
  35. 2026-09-26 02:20 UTCGHSA enrichment
  36. 2026-09-25 15:24 UTCEG score recompute
  37. 2026-09-25 15:24 UTCGHSA enrichment
  38. 2026-09-25 14:52 UTCEG score recompute▲ 7.80
  39. 2026-09-25 14:52 UTCGHSA enrichment
  40. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  41. 2026-09-25 11:30 UTCNVD update
  42. 2026-09-25 10:38 UTCEG score recompute
  43. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97612?
CVE-2026-97612 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mpls: clear inner_protocol when the last label is popped skbmplspush() records the pre-encapsulation network header once, gated on !skb->innerprotocol. skbmpls_pop() never clears that record, so it outlives the encapsulation…
When was CVE-2026-97612 disclosed?
CVE-2026-97612 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-97612 actively exploited?
CVE-2026-97612 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97612?
CVE-2026-97612 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-97612?
No fix for CVE-2026-97612 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-97612 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-97612

Explore →

Is Your Infrastructure Affected by CVE-2026-97612?

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

Book a Demo →Browse All CVEs