Skip to main content

Linux Kernel CVE-2026-53213

| EUVDEUVD-2026-39304 MEDIUM
Memory Leak (CWE-401)
2026-06-25 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-3886-873f-6xpf
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
2.5 LOW

AC:H because exploitation requires krealloc() failure under memory pressure, a non-default condition; A:L for gradual incremental leak rather than immediate denial of service.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 02, 2026 - 23:18 vuln.today
CVSS changed
Jul 02, 2026 - 21:07 NVD
5.5 (MEDIUM)
Patch available
Jun 25, 2026 - 10:32 EUVD
CVE Published
Jun 25, 2026 - 09:16 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 25, 2026 - 09:16 nvd
MEDIUM 5.5

DescriptionNVD

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().

AnalysisAI

Memory leak in the Linux kernel's drm/vc4 (Broadcom VideoCore IV DRM) driver allows a local low-privileged user to gradually exhaust kernel memory under allocation-failure conditions. The flaw arises because the return value of krealloc() is assigned directly back to the original pointer without a NULL check - if krealloc() fails and returns NULL, the reference to the previously allocated buffer is silently overwritten, permanently leaking that memory. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Authenticate as low-privilege local user
Delivery
Access vc4 DRM device interface
Exploit
Induce system memory pressure
Execution
Trigger krealloc() failure in vc4 driver code path
Persist
Kernel pointer overwritten with NULL, buffer leaked
Impact
Repeat to accumulate heap memory exhaustion

Vulnerability AssessmentAI

Exploitation Exploitation requires: (1) local authenticated access to the target system with at least low-privilege credentials (CVSS PR:L); (2) the target system must have Broadcom VideoCore IV GPU hardware present (e.g., Raspberry Pi) with the drm/vc4 kernel module loaded; (3) system must be under sufficient memory pressure that krealloc() returns NULL - this is a transient kernel-internal condition not reliably triggered by normal user-space operations. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment Real-world risk is low-to-moderate despite the CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario A local unprivileged user on a Raspberry Pi system triggers repeated DRM/KMS operations through the vc4 driver while the system is under memory pressure, causing krealloc() to return NULL in the affected code path. Each such failure leaks a kernel heap buffer whose size is determined by the GPU memory allocation request, and over time the accumulated leaks degrade available kernel memory, potentially destabilizing long-running systems or contributing to OOM conditions. …
Remediation Apply the vendor-released patches for the relevant stable branch: Linux 5.15.210, 6.1.176, 6.6.143, 6.12.94, 7.0.13, 6.18.36, or 7.1 (final release). … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-53213 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy