CVE-2026-90071

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. 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/sched: sch_teql: restore skb->dev on the slave failure path

teql_master_xmit() sets skb->dev = slave before calling the slave's ndo_start_xmit(), but never restores it when that transmit fails. The skb then walks on to the next slave still pointing at the previous one.

If a later slave has no resolved neighbour, teql_resolve() hands the skb to neigh_event_send(), which queues it on that neighbour's arp_queue with the stale skb->dev. skb->dev holds no reference, so deleting the previous slave frees the net_device while the skb is still queued. Whatever runs next on that skb - arp_error_report() on timeout, or neigh_direct_output() -> dev_queue_xmit() once the neighbour resolves - causes a UAF like the one below:

BUG: KASAN: slab-use-after-free in __icmp_send (net/ipv4/icmp.c:914 (discriminator 2)) Read of size 4 at addr ffff888106e100b0 by task flood_packet/527 CPU: 0 UID: 0 PID: 527 Comm: flood_packet Not tainted 7.2.0-rc6-g594d90519502 #1 PREEMPT(lazy) Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace:

dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) ? __pfx__raw_spin_lock_irqsave (./include/asm-generic/qrwlock.h:122 (discriminator 4)) ? __icmp_send (net/ipv4/icmp.c:914 (discriminator 2)) kasan_report (mm/kasan/report.c:595) ? __icmp_send (net/ipv4/icmp.c:914 (discriminator 2)) __icmp_send (net/ipv4/icmp.c:914 (discriminator 2)) [...] ipv4_link_failure (net/ipv4/route.c:1251 net/ipv4/route.c:1258) ? __pfx_ipv4_link_failure (./include/linux/skbuff.h:4327) ? _raw_write_lock (./include/linux/instrumented.h:55 ./include/linux/atomic/atomic-instrumented.h:1301 ./include/asm-generic/qrwlock.h:98 ./include/linux/rwlock_api_smp.h:230 kernel/locking/spinlock.c:304) ? __pfx__raw_write_lock (kernel/locking/spinlock.c:175) arp_error_report (./include/net/dst.h:438 net/ipv4/arp.c:296) neigh_invalidate (net/core/neighbour.c:1077) neigh_timer_handler (net/core/neighbour.c:1169) [...] Allocated by task 505: kasan_save_stack (mm/kasan/common.c:57) kasan_save_track (mm/kasan/common.c:78) __kasan_kmalloc (mm/kasan/common.c:398 mm/kasan/common.c:415) __kvmalloc_node_noprof (./include/linux/kasan.h:263 mm/slub.c:5334 mm/slub.c:6905) alloc_netdev_mqs (net/core/dev.c:12055 (discriminator 2)) rtnl_create_link (net/core/rtnetlink.c:3721) rtnl_newlink (net/core/rtnetlink.c:3903 net/core/rtnetlink.c:4044 net/core/rtnetlink.c:4159) rtnetlink_rcv_msg (net/core/rtnetlink.c:7076) [...] Freed by task 536: kasan_save_stack (mm/kasan/common.c:57) kasan_save_track (mm/kasan/common.c:78) kasan_save_free_info (mm/kasan/generic.c:584) __kasan_slab_free (mm/kasan/common.c:253 mm/kasan/common.c:285) kfree (./include/linux/kasan.h:235 mm/slub.c:2677 mm/slub.c:6377 mm/slub.c:6692) device_release (drivers/base/core.c:2636) kobject_put (lib/kobject.c:689 lib/kobject.c:720 ./include/linux/kref.h:65 lib/kobject.c:737) netdev_run_todo (net/core/dev.c:11756) rtnl_dellink (net/core/rtnetlink.c:157 ./include/linux/rtnetlink.h:135 net/core/rtnetlink.c:3651) rtnetlink_rcv_msg (net/core/rtnetlink.c:7076) [...]

Fix this by restoring skb->dev to the master at the end of each slave's iteration.

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

Last Modified

September 18, 2026

Advisory Details (8)

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

net/sched: sch_teql: restore skb->dev on the slave failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_teql: restore skb->dev on the slave failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_teql: restore skb->dev on the slave failure path - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_teql: restore skb->dev on the slave failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96bc345a3f17543d0d92ada609e02198d6380e26
generic

net/sched: sch_teql: restore skb->dev on the slave failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1360bc93f5be1be3cf937ebea667b3418dd30a79
generic

net/sched: sch_teql: restore skb->dev on the slave failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cd75037948567193f7f5767176538822ce23873
generic

net/sched: sch_teql: restore skb->dev on the slave failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/012559cf3c67ce8825a31d4f66b040b6fbaf775e
generic

net/sched: sch_teql: restore skb->dev on the slave failure path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00d8a387b23b7831ad9919256a6b9caaa10f19c3

Vendor Advisories for CVE-2026-90071(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 40× in last 7d / 105× 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 105 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-90071?
CVE-2026-90071 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_teql: restore skb->dev on the slave failure path teqlmasterxmit() sets skb->dev = slave before calling the slave's ndostartxmit(), but never restores it when that transmit fails. The skb then walks on to the next…
When was CVE-2026-90071 disclosed?
CVE-2026-90071 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90071 actively exploited?
CVE-2026-90071 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-90071?
CVE-2026-90071 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-90071?
No fix for CVE-2026-90071 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-90071 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-90071

Explore →

Is Your Infrastructure Affected by CVE-2026-90071?

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

Book a Demo →Browse All CVEs