CVE-2026-53202

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

accel/ivpu: Fix signed integer truncation in IPC receive

Fix potential buffer overflow where firmware-supplied data_size is cast to signed int before being used in min_t(). Large unsigned values (>= 0x80000000) become negative, causing unsigned wraparound and oversized memcpy operations that can overflow the stack buffer.

Change min_t(int, ...) to min() as both values are unsigned and can be handled by min() without explicit cast.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 24, 2026

Advisory Details (4)

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

accel/ivpu: Fix signed integer truncation in IPC receive - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/ivpu: Fix signed integer truncation in IPC receive - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4788556d4dd9d717037e385de178974e9649231d
generic

accel/ivpu: Fix signed integer truncation in IPC receive - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45cb105b8642c65e9be286f7058e92314efe7ea3
generic

accel/ivpu: Fix signed integer truncation in IPC receive - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2821bf2b79e47f87e1dbdd9d25c78240965a97d6

Patch Availability(6)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Weakness Classification(2)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 64× 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.

Showing the most recent 100 of 255 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 07:35 UTCEG score recompute
  3. 2026-09-18 07:35 UTCVendor advisory
  4. 2026-09-18 07:35 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 01:25 UTCEG score recompute
  8. 2026-09-14 01:25 UTCVendor advisory
  9. 2026-09-14 01:25 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 09:43 UTCVendor advisory
  12. 2026-09-13 09:43 UTCGHSA enrichment
  13. 2026-09-12 15:58 UTCEG score recompute
  14. 2026-09-12 15:58 UTCVendor advisory
  15. 2026-09-12 15:58 UTCGHSA enrichment
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 13:47 UTCEPSS rescore
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 13:54 UTCEPSS rescore
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-30 19:40 UTCEG score recompute
  24. 2026-08-30 19:40 UTCVendor advisory
  25. 2026-08-30 19:40 UTCGHSA enrichment
Show 75 more
  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-28 00:02 UTCEG score recompute
  5. 2026-08-28 00:02 UTCVendor advisory
  6. 2026-08-28 00:02 UTCGHSA enrichment
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 01:28 UTCEG score recompute
  11. 2026-08-25 01:28 UTCVendor advisory
  12. 2026-08-25 01:28 UTCGHSA enrichment
  13. 2026-08-24 12:20 UTCEG score recompute
  14. 2026-08-24 12:20 UTCVendor advisory
  15. 2026-08-24 12:20 UTCGHSA enrichment
  16. 2026-08-24 04:31 UTCVendor advisory
  17. 2026-08-24 04:31 UTCGHSA enrichment
  18. 2026-08-23 13:26 UTCEG score recompute
  19. 2026-08-23 13:26 UTCVendor advisory
  20. 2026-08-23 13:26 UTCGHSA enrichment
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 23:51 UTCVendor advisory
  23. 2026-08-22 23:51 UTCGHSA enrichment
  24. 2026-08-22 10:46 UTCEG score recompute
  25. 2026-08-22 10:46 UTCVendor advisory
  26. 2026-08-22 10:46 UTCGHSA enrichment
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-21 13:21 UTCEG score recompute
  29. 2026-08-21 13:21 UTCVendor advisory
  30. 2026-08-21 13:21 UTCGHSA enrichment
  31. 2026-08-21 12:30 UTCEG score recompute
  32. 2026-08-21 12:30 UTCVendor advisory
  33. 2026-08-21 12:30 UTCGHSA enrichment
  34. 2026-08-21 09:21 UTCEG score recompute
  35. 2026-08-21 09:21 UTCVendor advisory
  36. 2026-08-21 09:21 UTCGHSA enrichment
  37. 2026-08-20 22:55 UTCEPSS rescore
  38. 2026-08-20 20:15 UTCVendor advisory
  39. 2026-08-20 20:15 UTCGHSA enrichment
  40. 2026-08-20 07:10 UTCEG score recompute
  41. 2026-08-20 07:10 UTCVendor advisory
  42. 2026-08-20 07:10 UTCGHSA enrichment
  43. 2026-08-19 17:04 UTCEPSS rescore
  44. 2026-08-19 14:50 UTCVendor advisory
  45. 2026-08-19 14:50 UTCGHSA enrichment
  46. 2026-08-19 01:33 UTCEG score recompute
  47. 2026-08-19 01:33 UTCVendor advisory
  48. 2026-08-19 01:33 UTCGHSA enrichment
  49. 2026-08-18 13:48 UTCEPSS rescore
  50. 2026-08-17 13:47 UTCEPSS rescore
  51. 2026-08-17 07:31 UTCVendor advisory
  52. 2026-08-17 07:31 UTCGHSA enrichment
  53. 2026-08-16 18:27 UTCEG score recompute
  54. 2026-08-16 18:27 UTCVendor advisory
  55. 2026-08-16 18:27 UTCGHSA enrichment
  56. 2026-08-16 14:56 UTCEPSS rescore
  57. 2026-08-16 04:42 UTCEG score recompute
  58. 2026-08-16 04:42 UTCVendor advisory
  59. 2026-08-16 04:42 UTCGHSA enrichment
  60. 2026-08-16 02:14 UTCEPSS rescore
  61. 2026-08-15 15:37 UTCVendor advisory
  62. 2026-08-15 15:37 UTCGHSA enrichment
  63. 2026-08-15 02:32 UTCEG score recompute
  64. 2026-08-15 02:32 UTCVendor advisory
  65. 2026-08-15 02:31 UTCGHSA enrichment
  66. 2026-08-15 01:30 UTCEPSS rescore
  67. 2026-08-14 13:26 UTCEG score recompute
  68. 2026-08-14 13:26 UTCVendor advisory
  69. 2026-08-14 13:26 UTCGHSA enrichment
  70. 2026-08-14 12:29 UTCEG score recompute
  71. 2026-08-14 12:29 UTCVendor advisory
  72. 2026-08-14 12:29 UTCGHSA enrichment
  73. 2026-08-14 02:41 UTCEG score recompute
  74. 2026-08-14 02:41 UTCVendor advisory
  75. 2026-08-14 02:41 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53202?
CVE-2026-53202 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix signed integer truncation in IPC receive Fix potential buffer overflow where firmware-supplied data_size is cast to signed int before being used in min_t(). Large unsigned values (>= 0x80000000) become negative,…
When was CVE-2026-53202 disclosed?
CVE-2026-53202 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53202 actively exploited?
CVE-2026-53202 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53202?
CVE-2026-53202 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53202?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53202, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53202

Explore →

Is Your Infrastructure Affected by CVE-2026-53202?

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