CVE-2026-53300

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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: 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(high)
EPSS
2.5%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 30, 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.

Data Freshness Timeline

(refreshed 33× in last 7d / 45× 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-07-07 00:45 UTCEG score recompute
  2. 2026-07-07 00:45 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 12:03 UTCEG score recompute
  6. 2026-07-06 12:03 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 23:19 UTCEG score recompute
  10. 2026-07-05 23:19 UTCGHSA enrichment
  11. 2026-07-05 10:36 UTCEG score recompute
  12. 2026-07-05 10:36 UTCGHSA enrichment
  13. 2026-07-04 21:55 UTCEG score recompute
  14. 2026-07-04 21:54 UTCGHSA enrichment
  15. 2026-07-04 09:13 UTCEG score recompute
  16. 2026-07-04 09:12 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 20:30 UTCEG score recompute
  20. 2026-07-03 20:30 UTCGHSA enrichment
  21. 2026-07-03 07:49 UTCEG score recompute
  22. 2026-07-03 07:49 UTCGHSA enrichment
  23. 2026-07-02 19:07 UTCEG score recompute
  24. 2026-07-02 19:07 UTCGHSA enrichment
  25. 2026-07-02 06:26 UTCEG score recompute
Show 20 more
  1. 2026-07-02 06:26 UTCGHSA enrichment
  2. 2026-07-01 17:43 UTCEG score recompute
  3. 2026-07-01 17:43 UTCGHSA enrichment
  4. 2026-07-01 05:02 UTCEG score recompute
  5. 2026-07-01 05:01 UTCGHSA enrichment
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 16:20 UTCEG score recompute
  8. 2026-06-30 16:20 UTCGHSA enrichment
  9. 2026-06-30 03:39 UTCEG score recompute
  10. 2026-06-30 03:38 UTCGHSA enrichment
  11. 2026-06-29 14:53 UTCEG score recompute 7.80
  12. 2026-06-29 14:53 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-26 21:37 UTCEG score recompute
  20. 2026-06-26 21:37 UTCGHSA enrichment

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 June 30, 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 2.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53300?
CVE-2026-53300 has a CVSS v3 base score of 7.8 (NVD).
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

Explore the affected products and dependency analysis for 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.