CVE-2026-53203

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 buffer overflow check in MS get_info_ioctl

Add validation that the info size returned from the metric stream info query is not exceeded when checked against the allocated buffer size. If the firmware returns a size larger than the buffer, reject the operation with -EOVERFLOW instead of proceeding with an incorrect buffer copy.

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

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (4)

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

accel/ivpu: Add buffer overflow check in MS get_info_ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/ivpu: Add buffer overflow check in MS get_info_ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/ivpu: Add buffer overflow check in MS get_info_ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/ivpu: Add buffer overflow check in MS get_info_ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e5047cc94bea1cc7b670b7f503358e9af0542df

Vendor Advisories for CVE-2026-53203(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53203?
CVE-2026-53203 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Add buffer overflow check in MS getinfoioctl Add validation that the info size returned from the metric stream info query is not exceeded when checked against the allocated buffer size. If the firmware returns a size…
When was CVE-2026-53203 disclosed?
CVE-2026-53203 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-53203 actively exploited?
CVE-2026-53203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53203?
CVE-2026-53203 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-53203?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53203, 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-53203

Explore →

Is Your Infrastructure Affected by CVE-2026-53203?

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