CVE-2024-53058

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-11-19. 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: 1%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data

In case the non-paged data of a SKB carries protocol header and protocol payload to be transmitted on a certain platform that the DMA AXI address width is configured to 40-bit/48-bit, or the size of the non-paged data is bigger than TSO_MAX_BUFF_SIZE on a certain platform that the DMA AXI address width is configured to 32-bit, then this SKB requires at least two DMA transmit descriptors to serve it.

For example, three descriptors are allocated to split one DMA buffer mapped from one piece of non-paged data: dma_desc[N + 0], dma_desc[N + 1], dma_desc[N + 2]. Then three elements of tx_q->tx_skbuff_dma[] will be allocated to hold extra information to be reused in stmmac_tx_clean(): tx_q->tx_skbuff_dma[N + 0], tx_q->tx_skbuff_dma[N + 1], tx_q->tx_skbuff_dma[N + 2]. Now we focus on tx_q->tx_skbuff_dma[entry].buf, which is the DMA buffer address returned by DMA mapping call. stmmac_tx_clean() will try to unmap the DMA buffer _ONLY_IF_ tx_q->tx_skbuff_dma[entry].buf is a valid buffer address.

The expected behavior that saves DMA buffer address of this non-paged data to tx_q->tx_skbuff_dma[entry].buf is: tx_q->tx_skbuff_dma[N + 0].buf = NULL; tx_q->tx_skbuff_dma[N + 1].buf = NULL; tx_q->tx_skbuff_dma[N + 2].buf = dma_map_single(); Unfortunately, the current code misbehaves like this: tx_q->tx_skbuff_dma[N + 0].buf = dma_map_single(); tx_q->tx_skbuff_dma[N + 1].buf = NULL; tx_q->tx_skbuff_dma[N + 2].buf = NULL;

On the stmmac_tx_clean() side, when dma_desc[N + 0] is closed by the DMA engine, tx_q->tx_skbuff_dma[N + 0].buf is a valid buffer address obviously, then the DMA buffer will be unmapped immediately. There may be a rare case that the DMA engine does not finish the pending dma_desc[N + 1], dma_desc[N + 2] yet. Now things will go horribly wrong, DMA is going to access a unmapped/unreferenced memory region, corrupted data will be transmited or iommu fault will be triggered :(

In contrast, the for-loop that maps SKB fragments behaves perfectly as expected, and that is how the driver should do for both non-paged data and paged frags actually.

This patch corrects DMA map/unmap sequences by fixing the array index for tx_q->tx_skbuff_dma[entry].buf when assigning DMA buffer address.

Tested and verified on DWXGMAC CORE 3.20a

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

November 19, 2024

Last Modified

August 5, 2026

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.133.132) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1072.70) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm (5.15.0.1070.66) @ jammy2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1075.71) @ jammy2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.133.143~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1075.74) @ jammy2026-05-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1075.81~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1073.73) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.134.145~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1078.80) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-05-23ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-23ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-05-23ubuntu
linuxKernel @ 5.15.171osv

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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u16.1.119-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (31 versions)6.1.119-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.11.7-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.11.7-1

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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 169 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-53058?
CVE-2024-53058 is a medium vulnerability published on November 19, 2024. In the Linux kernel, the following vulnerability has been resolved: net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data In case the non-paged data of a SKB carries protocol header and protocol payload to be transmitted on a certain platform that the DMA AXI address width is…
When was CVE-2024-53058 disclosed?
CVE-2024-53058 was first published in the National Vulnerability Database on November 19, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-53058 actively exploited?
CVE-2024-53058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.6% of all scored CVEs.
What is the CVSS score of CVE-2024-53058?
CVE-2024-53058 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-53058?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-53058, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-53058

Explore →

Is Your Infrastructure Affected by CVE-2024-53058?

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