In the Linux kernel, the following vulnerability has been resolved: drm/vc4: fix krealloc() memory leak Don't just overwrite the original pointer… (CVE-2026-53213)
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().
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's drm/vc4 component involves improper use of the krealloc() function, where the original pointer is overwritten directly with krealloc()'s return value without checking for NULL. If krealloc() returns NULL, the original pointer to allocated memory is lost, causing a memory leak (CWE-401). The patch corrects this by using a temporary pointer to check krealloc()'s return before assignment and recommends using krealloc_array() instead. This issue impacts availability due to memory leaks but does not affect confidentiality or integrity.
Potential Impact
The vulnerability leads to a memory leak in the kernel's drm/vc4 driver, which can degrade system availability or stability over time. There is no impact on confidentiality or integrity. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves updating the kernel code to properly handle krealloc() return values as described. Until patched, monitoring for memory leaks in the drm/vc4 driver may be prudent.
In the Linux kernel, the following vulnerability has been resolved: drm/vc4: fix krealloc() memory leak Don't just overwrite the original pointer… (CVE-2026-53213)
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().
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's drm/vc4 component involves improper use of the krealloc() function, where the original pointer is overwritten directly with krealloc()'s return value without checking for NULL. If krealloc() returns NULL, the original pointer to allocated memory is lost, causing a memory leak (CWE-401). The patch corrects this by using a temporary pointer to check krealloc()'s return before assignment and recommends using krealloc_array() instead. This issue impacts availability due to memory leaks but does not affect confidentiality or integrity.
Potential Impact
The vulnerability leads to a memory leak in the kernel's drm/vc4 driver, which can degrade system availability or stability over time. There is no impact on confidentiality or integrity. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves updating the kernel code to properly handle krealloc() return values as described. Until patched, monitoring for memory leaks in the drm/vc4 driver may be prudent.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3886-873f-6xpf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53213"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a46eca927e9c7971943a6b4
Added to database: 07/02/2026, 22:56:41 UTC
Last enriched: 07/02/2026, 23:02:05 UTC
Last updated: 07/31/2026, 19:24:47 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.