CVE-2026-53172

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 IFM region index out-of-bounds in command stream parser

NPU_SET_IFM_REGION extracts the region index with param & 0x7f, giving a maximum value of 127. However region_size[] and output_region[] in struct ethosu_validated_cmdstream_info are both sized to NPU_BASEP_REGION_MAX (8), giving valid indices [0..7].

Every other region assignment in the same switch uses param & 0x7: NPU_SET_OFM_REGION: st.ofm.region = param & 0x7; NPU_SET_IFM2_REGION: st.ifm2.region = param & 0x7; NPU_SET_WEIGHT_REGION: st.weight[0].region = param & 0x7; NPU_SET_SCALE_REGION: st.scale[0].region = param & 0x7;

The 0x7f mask on IFM is inconsistent and appears to be a typo.

feat_matrix_length() and calc_sizes() use the region index directly as an array subscript into the kzalloc'd info struct: info->region_size[fm->region] = max(...);

A userspace caller supplying NPU_SET_IFM_REGION with param > 7 causes a write up to 127*8 = 1016 bytes past the start of region_size[], corrupting adjacent kernel heap data.

Fix by applying the same & 0x7 mask used by all other region assignments.

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 IFM region index out-of-bounds in command stream parser - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/ethosu: fix IFM region index out-of-bounds in command stream parser - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00f547e0dfecf83014fb32bcba587c6b684c1362

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53172?
CVE-2026-53172 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/ethosu: fix IFM region index out-of-bounds in command stream parser NPUSETIFM_REGION extracts the region index with param & 0x7f, giving a maximum value of 127. However regionsize[] and outputregion[] in struct…
When was CVE-2026-53172 disclosed?
CVE-2026-53172 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-53172 actively exploited?
CVE-2026-53172 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-53172?
CVE-2026-53172 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53172?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53172, 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-53172

Explore →

Is Your Infrastructure Affected by CVE-2026-53172?

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

Start Free Scan →Browse All CVEs