CVE-2026-53329

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
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 PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 1, 2026

Last Modified

August 5, 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(3)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-0:4.18.0-553.156.1.el8_102026-08-17redhat
redhatkernel-rt-0:4.18.0-553.156.1.rt7.497.el8_102026-08-17redhat

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 ... 5.10.92-2 (55 versions)5.10.262-1—
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 (142 versions)7.0.13-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 16× in last 7d / 145× 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 226 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-53329?
CVE-2026-53329 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
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

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