Linux Kernel up to 7.0.12 drm krealloc temporary memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.62-

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 7.0.12. This vulnerability affects the function krealloc of the component drm. Such manipulation of the argument temporary leads to memory leak. This vulnerability is uniquely identified as CVE-2026-53213. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 7.0.12. Affected by this issue is the function krealloc of the component drm. The manipulation of the argument temporary with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability. CVE summarizes:

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

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-53213 since 06/09/2026. There are known technical details, but no exploit is available.

Upgrading to version 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36 or 7.0.13 eliminates this vulnerability. Applying the patch 30165a09f76eaf34951c818eb5d9d6e4771d76f6/fd87d6966041e33ef7d2e5dc59f9a52b71c6ae5f/e0ce103e89d61eef70edc1d1ae3bfd4c0aacbc2e/c034aa0b1ba5f49cbdf8ef193d6ec714d74aac27/4fc692dc6df5bc777cc1bcebf95179e28594875f/5d563a5da8717629ae72f9eadf1e0e340bd1658b is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.210/6.1.176/6.6.143/6.12.94/6.18.36/7.0.13
Patch: 30165a09f76eaf34951c818eb5d9d6e4771d76f6/fd87d6966041e33ef7d2e5dc59f9a52b71c6ae5f/e0ce103e89d61eef70edc1d1ae3bfd4c0aacbc2e/c034aa0b1ba5f49cbdf8ef193d6ec714d74aac27/4fc692dc6df5bc777cc1bcebf95179e28594875f/5d563a5da8717629ae72f9eadf1e0e340bd1658b

Timelineinfo

06/09/2026 CVE reserved
06/25/2026 +16 days Advisory disclosed
06/25/2026 +0 days VulDB entry created
06/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-53213 (🔒)
GCVE (CVE): GCVE-0-2026-53213
GCVE (VulDB): GCVE-100-373772

Entryinfo

Created: 06/25/2026 12:22
Changes: 06/25/2026 12:22 (60)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!