LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38612: staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel cleanup bug in the staging fbtft framebuffer code. Under certain allocation error paths, memory reserved for deferred I/O page references may not be freed. The sources do not provide a CVSS score, impact rating, or evidence of active exploitation.

Executive priority

Handle through normal kernel patch management unless local asset inventory shows fbtft use on critical systems. There is no source-backed evidence of active exploitation or severe business impact in the provided bundle.

Technical view

CVE-2025-38612 fixes a potential memory leak in fbtft_framebuffer_alloc(). After fb_info allocation succeeds, later error handling failed to free memory allocated by fb_deferred_io_init() for info->pagerefs. Kernel stable commits add cleanup on the error path.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the staging fbtft framebuffer driver code present and relevant allocation error paths reachable. The bundle lists Linux as affected across multiple stable versions, but does not identify specific distributions beyond Debian LTS references.

Exploitation context

The provided sources do not show public exploitation, KEV listing, exploit code, or attacker prerequisites. This appears to be a reliability/resource-leak issue rather than a clearly demonstrated privilege escalation or remote compromise path.

Researcher notes

The key evidence is the kernel commit description: a missed cleanup path after fb_deferred_io_init() allocates info->pagerefs. The affected-version data is broad and somewhat sparse, so validation should focus on kernel source/package backports and fbtft configuration.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check vendor or distribution kernel advisories for packaged update status.
  • Prioritize embedded or display-heavy systems using fbtft-related framebuffer support.
  • Track Debian LTS advisories if running affected Debian kernels.

Validation and detection

  • Inventory Linux kernel versions against the affected versions in the CVE record.
  • Confirm whether fbtft staging framebuffer support is built or loaded.
  • Verify deployed kernels include one of the referenced stable commits.
  • Review distribution advisories for backported fixes under existing kernel package versions.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38612 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
12Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc296d5f9957c03994a699d6739c27d4581a9f6c7, c296d5f9957c03994a699d6739c27d4581a9f6c7, c296d5f9957c03994a699d6739c27d4581a9f6c7, c296d5f9957c03994a699d6739c27d4581a9f6c7, c296d5f9957c03994a699d6739c27d4581a9f6c7, c296d5f9957c03994a699d6739c27d4581a9f6c7, c296d5f9957c03994a699d6739c27d4581a9f6c7, c296d5f9957c03994a699d6739c27d4581a9f6c7, c296d5f9957c03994a699d6739c27d4581a9f6c7unaffected
LinuxLinux4.0, 0, 5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.