CVE-2026-53173

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. 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:

accel/ethosu: fix OOB write in ethosu_gem_cmdstream_copy_and_validate()

The command stream parsing loop increments the index variable a second time when a 64-bit command word is encountered (bit 14 set), but does not re-check the loop bound before writing the second word:

for (i = 0; i < size / 4; i++) { bocmds[i] = cmds[0]; if (cmd & 0x4000) { i++; bocmds[i] = cmds[1]; /* unchecked */ } }

The buffer bocmds is backed by a DMA allocation of exactly size bytes from drm_gem_dma_create(ddev, size), giving valid indices [0, size/4-1].

When i == size/4 - 1 on entry to an iteration and bit 14 of cmds[0] is set, bocmds[size/4-1] is written in bounds, i is then incremented to size/4, and bocmds[size/4] writes four bytes past the end of the allocation.

Userspace controls both the buffer contents and the size argument via the ioctl, making this a userspace-triggerable heap out-of-bounds write.

Fix by checking the incremented index against the buffer bound before the second write and returning -EINVAL if the buffer is too small to contain the extended command.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
2.9%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (2)

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

accel/ethosu: fix OOB write in ethosu_gem_cmdstream_copy_and_validate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/ethosu: fix OOB write in ethosu_gem_cmdstream_copy_and_validate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-53173(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53173?
CVE-2026-53173 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/ethosu: fix OOB write in ethosugemcmdstreamcopyand_validate() The command stream parsing loop increments the index variable a second time when a 64-bit command word is encountered (bit 14 set), but does not re-check the loop…
When was CVE-2026-53173 disclosed?
CVE-2026-53173 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53173 actively exploited?
CVE-2026-53173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53173?
CVE-2026-53173 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53173?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53173, 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-53173

Explore →

Is Your Infrastructure Affected by CVE-2026-53173?

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