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

A fix is available — apply it.

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.

Patch Availability(4)

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
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(1)

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 10× in last 7d / 45× 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 218 total refreshes for this CVE.

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

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

See which npm, PyPI, Go, and Maven packages are affected by 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.