Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53213, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 6d45c81d229d71da54d374143e7d6abad4c0cf31 – < 30165a09f76eaf34951c818eb5d9d6e4771d76f6
    • affected 6d45c81d229d71da54d374143e7d6abad4c0cf31 – < fd87d6966041e33ef7d2e5dc59f9a52b71c6ae5f
    • affected 6d45c81d229d71da54d374143e7d6abad4c0cf31 – < e0ce103e89d61eef70edc1d1ae3bfd4c0aacbc2e
    • affected 6d45c81d229d71da54d374143e7d6abad4c0cf31 – < c034aa0b1ba5f49cbdf8ef193d6ec714d74aac27
    • affected 6d45c81d229d71da54d374143e7d6abad4c0cf31 – < 02f5e4db57c0cdd7bac89d503b301a093a0fa95c
    • affected 6d45c81d229d71da54d374143e7d6abad4c0cf31 – < 4fc692dc6df5bc777cc1bcebf95179e28594875f
    • affected 6d45c81d229d71da54d374143e7d6abad4c0cf31 – < 5d563a5da8717629ae72f9eadf1e0e340bd1658b
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53213 badge
[![CVE-2026-53213](https://cveledger.app/badge/CVE-2026-53213.svg)](https://cveledger.app/cve/CVE-2026-53213)

Record last updated .