CVE-2026-53213

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 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:

drm/vc4: fix krealloc() memory leak

Don't just overwrite the original pointer passed to krealloc() with its return value without checking latter:

MEM = krealloc(MEM, SZ, GFP);

If krealloc() returns NULL, that erases the pointer to the still allocated memory, hence leaks this memory. Instead, use a temporary variable, check it's not NULL and only then assign it to the original pointer:

TMP = krealloc(MEM, SZ, GFP); if (!TMP) return; MEM = TMP;

While on it, use krealloc_array().

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (7)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

drm/vc4: fix krealloc() memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/vc4: fix krealloc() memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/vc4: fix krealloc() memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/vc4: fix krealloc() memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d563a5da8717629ae72f9eadf1e0e340bd1658b
generic

drm/vc4: fix krealloc() memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4fc692dc6df5bc777cc1bcebf95179e28594875f
generic

drm/vc4: fix krealloc() memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30165a09f76eaf34951c818eb5d9d6e4771d76f6
generic

drm/vc4: fix krealloc() memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02f5e4db57c0cdd7bac89d503b301a093a0fa95c

Vendor Advisories for CVE-2026-53213(2)

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 10× in last 7d / 78× 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-26 15:12 UTCEG score recompute
  2. 2026-07-26 15:12 UTCVendor advisory
  3. 2026-07-26 15:12 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:19 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-17 00:38 UTCVendor advisory
  17. 2026-07-17 00:38 UTCGHSA enrichment
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 01:23 UTCVendor advisory
  20. 2026-07-16 01:23 UTCGHSA enrichment
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 02:12 UTCGHSA enrichment
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 57 more
  1. 2026-07-14 03:00 UTCVendor advisory
  2. 2026-07-14 03:00 UTCGHSA enrichment
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 03:49 UTCVendor advisory
  7. 2026-07-13 03:48 UTCGHSA enrichment
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-12 04:37 UTCVendor advisory
  10. 2026-07-12 04:37 UTCGHSA enrichment
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 05:26 UTCVendor advisory
  14. 2026-07-11 05:26 UTCGHSA enrichment
  15. 2026-07-10 06:15 UTCVendor advisory
  16. 2026-07-10 06:15 UTCGHSA enrichment
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 07:02 UTCVendor advisory
  20. 2026-07-09 07:02 UTCGHSA enrichment
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 07:51 UTCVendor advisory
  24. 2026-07-08 07:51 UTCGHSA enrichment
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-07 13:46 UTCEPSS rescore
  27. 2026-07-07 08:41 UTCVendor advisory
  28. 2026-07-07 08:41 UTCGHSA enrichment
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 16:27 UTCEPSS rescore
  31. 2026-07-06 09:28 UTCVendor advisory
  32. 2026-07-06 09:28 UTCGHSA enrichment
  33. 2026-07-05 10:15 UTCVendor advisory
  34. 2026-07-05 10:15 UTCGHSA enrichment
  35. 2026-07-05 02:31 UTCEPSS rescore
  36. 2026-07-05 02:30 UTCEPSS rescore
  37. 2026-07-04 11:03 UTCEG score recompute 5.50
  38. 2026-07-04 11:03 UTCVendor advisory
  39. 2026-07-04 11:03 UTCGHSA enrichment
  40. 2026-07-04 06:31 UTCEPSS rescore
  41. 2026-07-04 06:31 UTCEPSS rescore
  42. 2026-07-02 22:05 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  43. 2026-07-01 15:07 UTCEPSS rescore
  44. 2026-07-01 10:45 UTCVendor advisory
  45. 2026-07-01 10:44 UTCGHSA enrichment
  46. 2026-06-30 23:22 UTCEPSS rescore
  47. 2026-06-29 14:06 UTCEPSS rescore
  48. 2026-06-29 14:06 UTCEPSS rescore
  49. 2026-06-28 14:07 UTCEPSS rescore
  50. 2026-06-28 10:26 UTCVendor advisory
  51. 2026-06-28 10:26 UTCGHSA enrichment
  52. 2026-06-28 04:56 UTCEPSS rescore
  53. 2026-06-28 04:56 UTCEPSS rescore
  54. 2026-06-27 03:08 UTCEPSS rescore
  55. 2026-06-25 13:49 UTCEPSS rescore
  56. 2026-06-25 10:07 UTCEG score recompute
  57. 2026-06-25 10:07 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53213?
CVE-2026-53213 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/vc4: fix krealloc() memory leak Don't just overwrite the original pointer passed to krealloc() with its return value without checking latter: MEM = krealloc(MEM, SZ, GFP); If krealloc() returns NULL, that erases the pointer to…
When was CVE-2026-53213 disclosed?
CVE-2026-53213 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-53213 actively exploited?
CVE-2026-53213 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 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53213?
CVE-2026-53213 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53213, 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-53213

Explore →

Is Your Infrastructure Affected by CVE-2026-53213?

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