CVE-2026-53213
drm/vc4: fix krealloc() memory leak
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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().
Timeline
- CVE published
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.8
References 7
git.kernel.org
- stable/c/30165a09f76eaf34951c818eb5d9d6e4771d76f6
- stable/c/fd87d6966041e33ef7d2e5dc59f9a52b71c6ae5f
- stable/c/e0ce103e89d61eef70edc1d1ae3bfd4c0aacbc2e
- stable/c/c034aa0b1ba5f49cbdf8ef193d6ec714d74aac27
- stable/c/02f5e4db57c0cdd7bac89d503b301a093a0fa95c
- stable/c/4fc692dc6df5bc777cc1bcebf95179e28594875f
- stable/c/5d563a5da8717629ae72f9eadf1e0e340bd1658b