Description
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().
Published: 2026-06-25
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The driver incorrectly assigns the result of krealloc to the original pointer without checking if the call returned NULL, destroying the reference to the previously allocated memory and leaking that memory block. This is a Memory Leak (CWE‑401) vulnerability that, if repeatedly exploited, can exhaust system memory and lead to denial‑of‑service. The vulnerability is limited to a loss of confidentiality, integrity and availability due to resource depletion.

Affected Systems

The flaw exists in the Linux kernel’s DRM driver for the VC4 GPU. Any Linux system running a kernel version that includes the legacy drm/vc4 driver without the patch is affected. The patch is referenced by commit identifiers in the provided URLs, but specific kernel versions are not enumerated.

Risk and Exploitability

No CVSS score or EPSS score is present, and the vulnerability is not listed in the CISA KEV catalog. Inferred attack vector would be local kernel exploitation, as an attacker must trigger the faulty krealloc path within the DRM driver, which does not provide arbitrary code execution. The risk is primarily denial‑of‑service via memory exhaustion, and the likelihood of exploitation is low unless the attacker has privileged access or can interact with the driver.

Generated by OpenCVE AI on June 25, 2026 at 11:24 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the patch referenced by the provided commit URLs
  • Reboot the system after updating to ensure the patched driver is loaded
  • Monitor system memory usage and GPU activity for signs of memory leakage

Generated by OpenCVE AI on June 25, 2026 at 11:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 25 Jun 2026 11:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-401

Thu, 25 Jun 2026 09:15:00 +0000

Type Values Removed Values Added
Description 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().
Title drm/vc4: fix krealloc() memory leak
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-06-25T08:39:17.552Z

Reserved: 2026-06-09T07:44:35.392Z

Link: CVE-2026-53213

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-25T11:30:06Z

Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime