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-2025-38612staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc()

Description

In the Linux kernel, the following vulnerability has been resolved: staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc() In the error paths after fb_info structure is successfully allocated, the memory allocated in fb_deferred_io_init() for info->pagerefs is not freed. Fix that by adding the cleanup function on the error path.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 9 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-2025-38612, 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.19% · top 91% of all CVEs (17 Nov 2026)
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 c296d5f9957c03994a699d6739c27d4581a9f6c7 – < 83ea0c7b8d12c67f6c4703d6c458627a7fc45fc0
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < c3b1c45c48117ed4d8797ee89d1155f16b72d490
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < 3290f62f23fae05f2ec34085eb86dfb3648ef91f
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < 6f9e2cf9e9c1a891a683329af35bb33ed9d38b5f
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < b31cf6f7716a5d3e4461763f32d812acdaec6e74
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < a3177955f8da3c826a18b75e54881e2e9a9c96f1
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < 6771f121ae87490ddc19eabb7450383af9e01b6d
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < 47b3d6e8921bbb7b65c2dab8eaa8864901848c1c
    • affected c296d5f9957c03994a699d6739c27d4581a9f6c7 – < eb2cb7dab60f9be0b435ac4a674255429a36d72c
  • Linux · Linux

    • affected 4.0
    • unaffected < 4.0
    • unaffected 5.4.297 – ≤ 5.4.*
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.148 – ≤ 6.1.*
    • unaffected 6.6.102 – ≤ 6.6.*
    • unaffected 6.12.42 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .