dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53329

HIGH · 7.0 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 5.10.260 / 5.15.210 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click Patch available 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In drm/amd/display's dal_vector_reserve(), the allocation size is computed as 'capacity * struct_size' using uint32_t arithmetic, which can silently wrap to a small value on integer overflow. This causes krealloc to allocate a smaller buffer than requested, leading to heap overflows when subsequent vector appends write beyond the allocated boundary.

MitigationReplace krealloc() with krealloc_array() in dal_vector_reserve() to enable built-in overflow checking, which returns NULL on multiplication overflow instead of silently wrapping.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.15, < 5.10.260>= 5.11, < 5.15.210>= 5.16, < 6.1.176>= 6.2, < 6.6.143>= 6.7, < 6.12.94>= 6.13, < 6.18.36>= 6.19, < 7.0.13= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify kernel version
    Run 'uname -r' or 'cat /proc/version' to obtain the running kernel version
    Affected if The kernel version is older than the version containing commit 37668568641ccc4cc1dbca4923d0a16609dd5707 (the fix) and the AMD display driver is in use
  2. Determine if AMD display driver is loaded
    Check for AMD GPU drivers in kernel modules via 'lsmod | grep -i amd' or 'modinfo drm' and look for dal-related modules
    Affected if AMD display driver (dal_vector_reserve code path) is present and active in the kernel
  3. Check for krealloc usage in display driver
    Inspect the kernel source file containing dal_vector_reserve() - look for krealloc() calls that multiply capacity * struct_size without overflow checking
    Affected if The vulnerable krealloc() pattern (capacity * struct_size) exists without krealloc_array() protection
  4. Verify fix presence in source
    Search the kernel source for the specific commit 37668568641ccc4cc1dbca4923d0a16609dd5707 or look for krealloc_array() usage in the dal_vector_reserve function
    Affected if The fix (krealloc_array() replacement) is not present in the kernel source code

A system is affected if it runs a kernel version prior to the fix commit AND uses the AMD display driver with the vulnerable dal_vector_reserve() function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.260 / 5.15.210 / 6.1.176 or later
Fixed in 5.10.2605.15.2106.1.176
Vendor patch git.kernel.org →
Interim mitigation

Replace krealloc() with krealloc_array() in dal_vector_reserve() to enable built-in overflow checking, which returns NULL on multiplication overflow instead of silently wrapping.

Recommended fix High confidence

Upgrade to kernel version 5.10.260, 5.15.210, 6.1.176, or 6.6.143 or later (6.6.y recommended for longest support)

  1. 1. Identify the current running kernel version using 'uname -r' or 'cat /proc/version'
  2. 2. Determine which Linux distribution kernel package is in use (e.g., from vendor like Red Hat, Ubuntu, Debian, or upstream)
  3. 3. For upstream/stock kernels: upgrade to kernel version 5.10.260 or higher (if using 5.10.x), 5.15.210 or higher (if using 5.15.x), 6.1.176 or higher (if using 6.1.x), or 6.6.143 or higher (if using 6.2+)
  4. 4. For distribution kernels: apply the vendor's security update that includes this fix (refer to distribution vendor security advisories)
  5. 5. After installation, reboot the system to load the fixed kernel
  6. 6. Verify the new kernel version is running using 'uname -r'
Caveat Kernel upgrades may introduce compatibility changes with proprietary drivers or older user-space tools; ensure critical applications are tested

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53329 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data