CVE-2026-97953

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.0Exploit: 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: fix TX descriptor availability check for TSO traffic

stmmac_tso_xmit() estimates the number of free TX descriptors required by a TSO skb as:

(skb->len - proto_hdr_len) / TSO_MAX_BUFF_SIZE + 1

which assumes the payload is split into TSO_MAX_BUFF_SIZE chunks. This underestimates the descriptors actually consumed by stmmac_tso_allocator(), since each fragment is mapped individually and so it needs at least one descriptor regardless of its size. Moreover, one descriptor is used for the L2/L3/L4 headers and, when the MSS changes, one more is consumed for the MSS context descriptor. For a highly fragmented TSO skb the check can therefore pass even when the ring has too few free slots. stmmac_tso_allocator() then writes past the available descriptors, overwriting descriptors still owned by the DMA engine, corrupting the TX ring. Add stmmac_tso_get_num_desc() to compute the exact number of descriptors needed for the header, the linear payload and each fragment, plus the MSS context descriptor when required, and use it in the availability check.

CVSS v3
7.0
EG Score
7.0HIGHhigh confidence
EG Risk
36
EG Risk 36/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
Severity70% × 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.4%
EPSS %ILE
32nd
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

September 25, 2026

Advisory Details (4)

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

net: stmmac: fix TX descriptor availability check for TSO traffic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e38d732ec67a5b1f9a56e6c73add480c4b6030a
generic

net: stmmac: fix TX descriptor availability check for TSO traffic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65820fc743eae322f7f94f6a64d07861211d4b21
generic

net: stmmac: fix TX descriptor availability check for TSO traffic - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: stmmac: fix TX descriptor availability check for TSO traffic - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

Frequently asked(5)

What is CVE-2026-97953?
CVE-2026-97953 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TX descriptor availability check for TSO traffic stmmactsoxmit() estimates the number of free TX descriptors required by a TSO skb as: (skb->len - protohdrlen) / TSOMAXBUFF_SIZE + 1 which assumes the payload is…
When was CVE-2026-97953 disclosed?
CVE-2026-97953 was first published 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-97953 actively exploited?
CVE-2026-97953 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97953?
CVE-2026-97953 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97953?
No fix for CVE-2026-97953 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-97953 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-97953

Explore →

Is Your Infrastructure Affected by CVE-2026-97953?

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