CVE-2026-31658

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit()

When dma_map_single() fails in tse_start_xmit(), the function returns NETDEV_TX_OK without freeing the skb. Since NETDEV_TX_OK tells the stack the packet was consumed, the skb is never freed, leaking memory on every DMA mapping failure.

Add dev_kfree_skb_any() before returning to properly free the skb.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

April 24, 2026

Last Modified

July 14, 2026

Advisory Details (10)

Auto-updated Jul 17, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f3ec44aeb58501d11834048d5d0dbaeacb6d4e7
generic

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6dede3967619b5944003227a5d09fdc21ed57d10
generic

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60f462cd2716d86bd2174f9d5e035c9278f30480
generic

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3aca300e88afe56afb000cdc4c65383014fb17f9
generic

net: altera-tse: fix skb leak on DMA mapping error in tse_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2eb9d67704ca8f1101f7435b85f113ede471f9f2

Vendor Advisories for CVE-2026-31658(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 47× 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 137 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31658?
CVE-2026-31658 is a medium vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: net: altera-tse: fix skb leak on DMA mapping error in tsestartxmit() When dmamapsingle() fails in tsestartxmit(), the function returns NETDEVTXOK without freeing the skb. Since NETDEVTXOK tells the stack the packet was consumed,…
When was CVE-2026-31658 disclosed?
CVE-2026-31658 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31658 actively exploited?
CVE-2026-31658 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-31658?
CVE-2026-31658 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31658?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31658, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-31658

Explore →

Is Your Infrastructure Affected by CVE-2026-31658?

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