CVE-2026-53300

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

net: enetc: fix NTMP DMA use-after-free issue

The AI-generated review reported a potential DMA use-after-free issue [1]. If netc_xmit_ntmp_cmd() times out and returns an error, the pending command is not explicitly aborted, while ntmp_free_data_mem() unconditionally frees the DMA buffer. If the buffer has already been reallocated elsewhere, this may lead to silent memory corruption. Because the hardware eventually processes the pending command and perform a DMA write of the response to the physical address of the freed buffer.

To resolve this issue, this patch does the following modifications:

  • Convert cbdr->ring_lock from a spinlock to a mutex

The lock was originally a spinlock in case NTMP operations might be invoked from atomic context. After downstream support for all NTMP tables, no such usage has materialized. A mutex lock is now required because the driver now needs to reclaim used BDs and release associated DMA memory within the lock's context, while dma_free_coherent() might sleep.

  • Introduce software command BD (struct netc_swcbd)

The hardware write-back overwrites the addr and len fields of the BD, so the driver cannot rely on the hardware BD to free the associated DMA memory. The driver now maintains a software shadow BD storing the DMA buffer pointer, DMA address, and size. And netc_xmit_ntmp_cmd() only reclaims older BDs when the number of used BDs reaches NETC_CBDR_CLEAN_WORK (16). The software BD enables correct DMA memory release. With this, struct ntmp_dma_buf and ntmp_free_data_mem() are no longer needed and are removed.

  • Require callers to hold ring_lock across netc_xmit_ntmp_cmd()

netc_xmit_ntmp_cmd() releases the ring_lock before the caller finishes consuming the response. At this point, if a concurrent thread submits a new command, it may trigger ntmp_clean_cbdr() and free the DMA buffer while it is still in use. Move ring_lock ownership to the caller to ensure the response buffer cannot be reclaimed prematurely. So the helpers ntmp_select_and_lock_cbdr() and ntmp_unlock_cbdr() are added.

These changes eliminate the DMA use-after-free condition and ensure safe and consistent BD reclamation and DMA buffer lifecycle management.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 26, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

net: enetc: fix NTMP DMA use-after-free issue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/655d9ce9b1d3db0aa5271acb5e5101c66bd0d58b
generic

net: enetc: fix NTMP DMA use-after-free issue - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: enetc: fix NTMP DMA use-after-free issue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37c8933064be714ee672b0a0523c2fd045b73b3d

Vendor Advisories for CVE-2026-53300(1)

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

Patch Availability(8)

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

Weakness Classification(1)

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

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 8× in last 7d / 87× 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 249 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53300?
CVE-2026-53300 is a high vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: net: enetc: fix NTMP DMA use-after-free issue The AI-generated review reported a potential DMA use-after-free issue [1]. If netcxmitntmp_cmd() times out and returns an error, the pending command is not explicitly aborted, while…
When was CVE-2026-53300 disclosed?
CVE-2026-53300 was first published in the National Vulnerability Database on June 26, 2026, 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-2026-53300 actively exploited?
CVE-2026-53300 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53300?
CVE-2026-53300 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53300, 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-2026-53300

Explore →

Is Your Infrastructure Affected by CVE-2026-53300?

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