CVE-2026-93250

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. 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:

vxlan: mdb: Fix use-after-free in vxlan_mdb_flush()

vxlan_mdb_flush() iterates over the MDB entries using hlist_for_each_entry_safe(), which only tolerates the removal of the current entry. Contrary to the comment above the loop, the removal of an entry can trigger the removal of another entry.

Flushing the remotes of a (*, G) entry also removes the (S, G) entries that were created for its source list, once they are left without remotes:

vxlan_mdb_remotes_flush() -> vxlan_mdb_remote_del() -> vxlan_mdb_remote_srcs_del() -> vxlan_mdb_remote_src_del() -> vxlan_mdb_remote_src_fwd_del() -> __vxlan_mdb_del() -> vxlan_mdb_entry_put()

Such an entry can be located after the (*, G) entry in the list, as vxlan_mdb_entry_get() returns an existing entry without moving it to the head of the list. This order is obtained by adding the (S, G) entry before the (*, G) entry, the latter with NLM_F_REPLACE, as the addition of the source otherwise fails with -EEXIST. The (S, G) entry is then the entry saved by hlist_for_each_entry_safe() and it is freed while the (*, G) entry is processed. The next iteration calls hlist_del() on it again, writing LIST_POISON1 to LIST_POISON2 [1].

Besides device deletion, the flush is also reachable from RTM_DELMDB with NLM_F_BULK.

Fix by re-reading the next entry after the remotes were flushed. The current entry cannot be removed by this flush, as source lists can only be configured on (*, G) entries and the removed entries are (S, G) entries. It is therefore still linked and its next pointer reflects the removals.

[1] BUG: KASAN: wild-memory-access in vxlan_mdb_entry_put.part.0+0x328/0x588 Write of size 8 at addr dead000000000122 by task ip/327

CPU: 3 UID: 1000 PID: 327 Comm: ip Not tainted 7.2.0-rc7 #2 PREEMPT Call trace: vxlan_mdb_entry_put.part.0+0x328/0x588 vxlan_mdb_flush+0x1d8/0x25c vxlan_mdb_fini+0x8c/0x100 vxlan_uninit+0x1c/0x7c unregister_netdevice_many_notify+0x954/0xd4c rtnl_dellink+0x210/0x530 rtnetlink_rcv_msg+0x434/0x4d0 netlink_rcv_skb+0xc4/0x204 rtnetlink_rcv+0x18/0x24 netlink_unicast+0x4b8/0x548 netlink_sendmsg+0x29c/0x560 ____sys_sendmsg+0x390/0x3ec ___sys_sendmsg+0x114/0x188 __sys_sendmsg+0xf0/0x178 __arm64_sys_sendmsg+0x48/0x60 invoke_syscall.constprop.0+0x58/0x180 el0_svc_common.constprop.0+0x74/0x140 do_el0_svc+0x30/0x40 el0_svc+0x38/0x98 el0t_64_sync_handler+0xa0/0xe4 el0t_64_sync+0x198/0x19c

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 24, 2026

Last Modified

September 25, 2026

Advisory Details (5)

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

vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e6b705bc162fc7257645725a7d2cf6c71250318

Vendor Advisories for CVE-2026-93250(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
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 42× in last 7d / 60× 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:01 UTCEG score recompute
  2. 2026-10-05 06:01 UTCVendor advisory
  3. 2026-10-05 06:01 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 18:34 UTCVendor advisory
  6. 2026-10-04 18:34 UTCGHSA enrichment
  7. 2026-10-04 07:01 UTCVendor advisory
  8. 2026-10-04 07:01 UTCGHSA enrichment
  9. 2026-10-03 19:35 UTCEG score recompute
  10. 2026-10-03 19:35 UTCVendor advisory
  11. 2026-10-03 19:35 UTCGHSA enrichment
  12. 2026-10-03 08:10 UTCVendor advisory
  13. 2026-10-03 08:09 UTCGHSA enrichment
  14. 2026-10-02 20:39 UTCEG score recompute
  15. 2026-10-02 20:39 UTCVendor advisory
  16. 2026-10-02 20:39 UTCGHSA enrichment
  17. 2026-10-02 09:10 UTCVendor advisory
  18. 2026-10-02 09:10 UTCGHSA enrichment
  19. 2026-10-01 21:44 UTCEG score recompute
  20. 2026-10-01 21:44 UTCVendor advisory
  21. 2026-10-01 21:44 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 10:15 UTCVendor advisory
  24. 2026-10-01 10:15 UTCGHSA enrichment
  25. 2026-09-30 22:49 UTCEG score recompute
Show 35 more
  1. 2026-09-30 22:49 UTCVendor advisory
  2. 2026-09-30 22:49 UTCGHSA enrichment
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-30 11:23 UTCVendor advisory
  5. 2026-09-30 11:23 UTCGHSA enrichment
  6. 2026-09-29 23:57 UTCEG score recompute
  7. 2026-09-29 23:57 UTCVendor advisory
  8. 2026-09-29 23:56 UTCGHSA enrichment
  9. 2026-09-29 12:15 UTCVendor advisory
  10. 2026-09-29 12:15 UTCGHSA enrichment
  11. 2026-09-29 00:49 UTCEG score recompute
  12. 2026-09-29 00:49 UTCVendor advisory
  13. 2026-09-29 00:48 UTCGHSA enrichment
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 13:20 UTCVendor advisory
  17. 2026-09-28 13:20 UTCGHSA enrichment
  18. 2026-09-28 01:54 UTCGHSA enrichment
  19. 2026-09-27 14:28 UTCEG score recompute
  20. 2026-09-27 14:28 UTCGHSA enrichment
  21. 2026-09-27 13:49 UTCEPSS rescore
  22. 2026-09-27 03:03 UTCEG score recompute
  23. 2026-09-27 03:03 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 15:36 UTCGHSA enrichment
  26. 2026-09-26 04:10 UTCEG score recompute
  27. 2026-09-26 04:10 UTCGHSA enrichment
  28. 2026-09-25 16:44 UTCEG score recompute
  29. 2026-09-25 16:44 UTCGHSA enrichment
  30. 2026-09-25 05:18 UTCEG score recompute▲ 7.80
  31. 2026-09-25 05:18 UTCGHSA enrichment
  32. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  33. 2026-09-24 16:30 UTCNVD update
  34. 2026-09-24 15:57 UTCEG score recompute
  35. 2026-09-24 15:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93250?
CVE-2026-93250 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: vxlan: mdb: Fix use-after-free in vxlanmdbflush() vxlanmdbflush() iterates over the MDB entries using hlistforeachentrysafe(), which only tolerates the removal of the current entry. Contrary to the comment above the loop, the…
When was CVE-2026-93250 disclosed?
CVE-2026-93250 was first published on September 24, 2026, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93250 actively exploited?
CVE-2026-93250 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-93250?
CVE-2026-93250 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-93250?
No fix for CVE-2026-93250 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-93250 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-93250

Explore →

Is Your Infrastructure Affected by CVE-2026-93250?

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

Book a Demo →Browse All CVEs