CVE-2026-90059

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: 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: stmmac: restore NET_IP_ALIGN in the RX DMA offset

Since the RX path was converted to zero-copy, the page pool page is handed to the stack directly as the skb head, and the offset the DMA engine writes at is what determines the alignment of the packet headers.

Before the conversion the payload was copied into an skb obtained from napi_alloc_skb(), which reserves NET_SKB_PAD + NET_IP_ALIGN. The conversion moved the headroom into stmmac_rx_offset() but did not carry over NET_IP_ALIGN, so on architectures where NET_IP_ALIGN is 2 the IP header now lands misaligned:

64 (NET_SKB_PAD) + 14 (ethernet) + 20 (IP) = 98

Same for the XDP branch:

256 (XDP_PACKET_HEADROOM) + 14 (ethernet) + 20 (IP) = 290

On ARM32 this is fatal, because ldm and ldrd trap on unaligned addresses even when CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS is set.

Any received echo request panics the machine, e.g:

Unhandled fault: alignment exception (0x001) at 0x81873062 Internal error: : 1 [#1] SMP ARM Hardware name: Altera SOCFPGA Arria10 PC is at icmp_echo+0x38/0xa8 LR is at icmp_rcv+0x22c/0x370 Call trace: icmp_echo from icmp_rcv+0x22c/0x370 icmp_rcv from ip_protocol_deliver_rcu+0x2c/0x224 ip_protocol_deliver_rcu from ip_local_deliver+0xc8/0x1a0 ip_local_deliver from ip_sublist_rcv_finish+0x3c/0x50 ip_sublist_rcv_finish from ip_list_rcv_finish+0x110/0x118 ip_list_rcv_finish from ip_list_rcv+0xc8/0xdc ip_list_rcv from __netif_receive_skb_list_core+0x170/0x1c0 ... napi_complete_done from stmmac_napi_poll_rx+0xcb0/0x1030 Code: e24dd068 e59020a0 e28dc010 e0822001 (e8920003) Kernel panic - not syncing: Fatal exception in interrupt

The faulting instruction is the ldm of *icmp_hdr(skb) in icmp_echo().

Fix by adding NET_IP_ALIGN back to the RX offset, which restores the alignment the stack used to get.

Note that commit a955318fe67e ("stmmac: align RX buffers") made a similar change in 2021 and was reverted by commit 12d125b4574b ("stmmac: Revert "stmmac: align RX buffers"") because it caused packet corruption. That patch raised the offset from 0 without adjusting the buffer size accounting, so the DMA engine could arguably write past the end of the RX buffers, though this was never root caused. Commit df542f669307 ("net: stmmac: Switch to zero-copy in non-XDP RX path") since derives the page pool allocation from stmmac_rx_offset(), so the extra bytes are accounted for.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
38
EG Risk 38/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
Severity75% × 45%
Exploitation1% × 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.6%
EPSS %ILE
47th
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 (3)

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

net: stmmac: restore NET_IP_ALIGN in the RX DMA offset - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: stmmac: restore NET_IP_ALIGN in the RX DMA offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ea42936416b29cca42b2c7bc7d3d3768f77c199
generic

net: stmmac: restore NET_IP_ALIGN in the RX DMA offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23680bf5f8c69c923546b84a8e6c401bef8b88fe

Vendor Advisories for CVE-2026-90059(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-90059?
CVE-2026-90059 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: net: stmmac: restore NETIPALIGN in the RX DMA offset Since the RX path was converted to zero-copy, the page pool page is handed to the stack directly as the skb head, and the offset the DMA engine writes at is what determines the…
When was CVE-2026-90059 disclosed?
CVE-2026-90059 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-90059 actively exploited?
CVE-2026-90059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90059?
CVE-2026-90059 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90059?
No fix for CVE-2026-90059 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-90059 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-90059

Explore →

Is Your Infrastructure Affected by CVE-2026-90059?

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

Book a Demo →Browse All CVEs