CVE-2026-53171

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.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 arithmetic issues in dma_length()

dma_length() derives DMA region usage from command stream values and updates region_size[]:

len = ((len + stride[0]) * size0 + stride[1]) * size1 region_size[region] = max(..., len + dma->offset)

Several arithmetic issues can corrupt the derived region size:

  • signed stride values may underflow when added to len
  • intermediate multiplications may overflow
  • len + dma->offset may overflow during region_size updates
  • dma_length() error returns were not validated by the caller

region_size[] is later used by ethosu_job.c to validate command stream accesses against GEM buffer sizes. Arithmetic wraparound can therefore under-report region usage and bypass the bounds validation.

Fix by validating signed additions, using overflow helpers for multiplications and offset updates, and propagating dma_length() failures to the caller.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
3.5%
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 arithmetic issues in dma_length() - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/ethosu: fix arithmetic issues in dma_length() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6bb73845d1855ceaf50e397175e5979a7bdf69bc

Vendor Advisories for CVE-2026-53171(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 40× in last 7d / 60× 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 08:28 UTCEG score recompute
  2. 2026-07-07 08:28 UTCGHSA enrichment
  3. 2026-07-06 21:03 UTCEG score recompute
  4. 2026-07-06 21:03 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 09:36 UTCEG score recompute
  8. 2026-07-06 09:36 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 22:15 UTCEG score recompute
  12. 2026-07-05 22:15 UTCGHSA enrichment
  13. 2026-07-05 10:54 UTCEG score recompute
  14. 2026-07-05 10:53 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 23:31 UTCEG score recompute
  18. 2026-07-04 23:31 UTCGHSA enrichment
  19. 2026-07-04 12:10 UTCEG score recompute
  20. 2026-07-04 12:09 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 00:45 UTCEG score recompute
  24. 2026-07-04 00:45 UTCGHSA enrichment
  25. 2026-07-03 13:16 UTCEG score recompute
Show 35 more
  1. 2026-07-03 13:16 UTCGHSA enrichment
  2. 2026-07-03 01:54 UTCEG score recompute
  3. 2026-07-03 01:54 UTCGHSA enrichment
  4. 2026-07-02 14:33 UTCEG score recompute
  5. 2026-07-02 14:33 UTCGHSA enrichment
  6. 2026-07-02 03:11 UTCEG score recompute
  7. 2026-07-02 03:11 UTCGHSA enrichment
  8. 2026-07-01 15:50 UTCEG score recompute
  9. 2026-07-01 15:50 UTCGHSA enrichment
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 04:29 UTCEG score recompute
  12. 2026-07-01 04:29 UTCGHSA enrichment
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-30 17:03 UTCEG score recompute
  15. 2026-06-30 17:03 UTCGHSA enrichment
  16. 2026-06-30 05:42 UTCEG score recompute
  17. 2026-06-30 05:42 UTCGHSA enrichment
  18. 2026-06-29 18:21 UTCEG score recompute
  19. 2026-06-29 18:21 UTCGHSA enrichment
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 06:58 UTCEG score recompute
  23. 2026-06-29 06:58 UTCGHSA enrichment
  24. 2026-06-28 19:37 UTCEG score recompute
  25. 2026-06-28 19:37 UTCGHSA enrichment
  26. 2026-06-28 14:07 UTCEPSS rescore
  27. 2026-06-28 08:16 UTCEG score recompute 8.80
  28. 2026-06-28 08:16 UTCGHSA enrichment
  29. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  30. 2026-06-28 04:56 UTCEPSS rescore
  31. 2026-06-28 04:56 UTCEPSS rescore
  32. 2026-06-27 03:08 UTCEPSS rescore
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-25 10:09 UTCEG score recompute
  35. 2026-06-25 10:09 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53171?
CVE-2026-53171 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/ethosu: fix arithmetic issues in dma_length() dma_length() derives DMA region usage from command stream values and updates region_size[]: len = ((len + stride[0]) size0 + stride[1]) size1 region_size[region] = max(..., len +…
When was CVE-2026-53171 disclosed?
CVE-2026-53171 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-53171 actively exploited?
CVE-2026-53171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53171?
CVE-2026-53171 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53171, 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-53171

Explore →

Is Your Infrastructure Affected by CVE-2026-53171?

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