Skip to main content
VulnerabilityPublished Updated

CVE-2026-53213: Linux kernel · drm/vc4: fix krealloc() memory leak

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fd87d6966041e33ef7d2e5dc59f9a52b71c6ae5f : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in fd87d6966041e33ef7d2e5dc59f9a52b71c6ae5f, e0ce103e89d61eef70edc1d1ae3bfd4c0aacbc2e, c034aa0b1ba5f49cbdf8ef193d6ec714d74aac27 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 6d45c81d229d71da54d374143e7d6abad4c0cf31, < fd87d6966041e33ef7d2e5dc59f9a52b71c6ae5f
Fixed in
  • fd87d6966041e33ef7d2e5dc59f9a52b71c6ae5f
LinuxLinuxAffected
  • ≥ 6d45c81d229d71da54d374143e7d6abad4c0cf31, < e0ce103e89d61eef70edc1d1ae3bfd4c0aacbc2e
Fixed in
  • e0ce103e89d61eef70edc1d1ae3bfd4c0aacbc2e
LinuxLinuxAffected
  • ≥ 6d45c81d229d71da54d374143e7d6abad4c0cf31, < c034aa0b1ba5f49cbdf8ef193d6ec714d74aac27
Fixed in
  • c034aa0b1ba5f49cbdf8ef193d6ec714d74aac27
LinuxLinuxAffected
  • ≥ 6d45c81d229d71da54d374143e7d6abad4c0cf31, < 30165a09f76eaf34951c818eb5d9d6e4771d76f6
Fixed in
  • 30165a09f76eaf34951c818eb5d9d6e4771d76f6
LinuxLinuxAffected
  • ≥ 6d45c81d229d71da54d374143e7d6abad4c0cf31, < 5d563a5da8717629ae72f9eadf1e0e340bd1658b
Fixed in
  • 5d563a5da8717629ae72f9eadf1e0e340bd1658b
LinuxLinuxAffected
  • ≥ 6d45c81d229d71da54d374143e7d6abad4c0cf31, < 4fc692dc6df5bc777cc1bcebf95179e28594875f
Fixed in
  • 4fc692dc6df5bc777cc1bcebf95179e28594875f

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

References

Community reviews

Loading reviews…