CVE-2026-53205

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: 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/ivpu: Add bounds checks for firmware log indices

Add validation that read and write indices in the firmware log buffer are within valid bounds (< data_size) before using them. If out-of-bounds indices are encountered (from firmware), clamp them to safe values instead of proceeding with invalid offsets.

This prevents potential out-of-bounds buffer access when firmware supplies invalid log indices.

CVSS v3
7.1
EG Score
7.1(high)
EPSS
3.0%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (4)

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

accel/ivpu: Add bounds checks for firmware log indices - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/ivpu: Add bounds checks for firmware log indices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ec70c0dbdf04392a26e03e38798a373934177be
generic

accel/ivpu: Add bounds checks for firmware log indices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5961c703414048f46818be8bbb11075a9a63fb4e
generic

accel/ivpu: Add bounds checks for firmware log indices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/535da9ad8420c3b686a642403d4147ff220255fd

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

Frequently asked(5)

What is CVE-2026-53205?
CVE-2026-53205 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Add bounds checks for firmware log indices Add validation that read and write indices in the firmware log buffer are within valid bounds (< data_size) before using them. If out-of-bounds indices are encountered (from…
When was CVE-2026-53205 disclosed?
CVE-2026-53205 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53205 actively exploited?
CVE-2026-53205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53205?
CVE-2026-53205 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-53205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53205, 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-53205

Explore →

Is Your Infrastructure Affected by CVE-2026-53205?

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