CVE-2026-53329

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: 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:

drm/amd/display: Use krealloc_array() in dal_vector_reserve()

[Why & How] dal_vector_reserve() computes the allocation size as "capacity * vector->struct_size" using uint32_t arithmetic, which can silently wrap to a small value on overflow. This would cause krealloc to return a smaller buffer than expected, leading to heap overflows on subsequent vector appends.

Replace krealloc() with krealloc_array() which performs an internal overflow check and returns NULL on wrap, preventing the issue.

(cherry picked from commit 37668568641ccc4cc1dbca4923d0a16609dd5707)

CVSS v3
7.0
EG Score
7.0(high)
EG Risk
36(Track)
EG Risk 36/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
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
3.3%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 23, 2026

Advisory Details (8)

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

drm/amd/display: Use krealloc_array() in dal_vector_reserve() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Use krealloc_array() in dal_vector_reserve() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Use krealloc_array() in dal_vector_reserve() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Use krealloc_array() in dal_vector_reserve() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Use krealloc_array() in dal_vector_reserve() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/201151e120f0062bcda21cad5d007b82725ad23b
generic

drm/amd/display: Use krealloc_array() in dal_vector_reserve() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Use krealloc_array() in dal_vector_reserve() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31180638a33acad12c863132704a76536fb66211
generic

drm/amd/display: Use krealloc_array() in dal_vector_reserve() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9540b0a4d13e4ede64ae1197d66a176d2149daa9

Vendor Advisories for CVE-2026-53329(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 17× in last 7d / 54× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:19 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 03:52 UTCEG score recompute
  10. 2026-07-19 03:52 UTCVendor advisory
  11. 2026-07-19 03:52 UTCGHSA enrichment
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-18 08:01 UTCEG score recompute▲ 7.00
  15. 2026-07-18 08:01 UTCVendor advisory
  16. 2026-07-18 08:01 UTCGHSA enrichment
  17. 2026-07-18 07:59 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  18. 2026-07-17 04:36 UTCVendor advisory
  19. 2026-07-17 04:36 UTCGHSA enrichment
  20. 2026-07-16 17:03 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-14 02:06 UTCVendor advisory
Show 29 more
  1. 2026-07-14 02:06 UTCGHSA enrichment
  2. 2026-07-13 22:31 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-10 23:35 UTCVendor advisory
  9. 2026-07-10 23:35 UTCGHSA enrichment
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-07 21:04 UTCGHSA enrichment
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:31 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 18:35 UTCGHSA enrichment
  24. 2026-07-04 12:27 UTCNVD update
  25. 2026-07-04 12:16 UTCMITRE cvelistV5
  26. 2026-07-04 06:31 UTCEPSS rescore
  27. 2026-07-04 06:31 UTCEPSS rescore
  28. 2026-07-01 16:04 UTCEG score recompute
  29. 2026-07-01 16:04 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53329?
CVE-2026-53329 is a high vulnerability published on July 1, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Use kreallocarray() in dalvector_reserve() [Why & How] dalvectorreserve() computes the allocation size as "capacity * vector->structsize" using uint32t arithmetic, which can silently wrap to a small value on…
When was CVE-2026-53329 disclosed?
CVE-2026-53329 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53329 actively exploited?
CVE-2026-53329 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53329?
CVE-2026-53329 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-53329?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53329, 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-53329

Explore →

Is Your Infrastructure Affected by CVE-2026-53329?

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

Start Free Scan →Browse All CVEs