LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38627: stm class: Fix a double free in stm_register_device()

In the Linux kernel, the following vulnerability has been resolved: stm class: Fix a double free in stm_register_device() The put_device(&stm->dev) call will trigger stm_device_release() which frees "stm" so the vfree(stm) on the next line is a double free.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38627 is a Linux kernel memory-management flaw in the stm class. Under an error path, the kernel can free the same object twice. That can cause instability and may carry security risk, but the provided sources do not give CVSS, prerequisites, or confirmed impact beyond the double-free condition.

Executive priority

Handle through the normal kernel security update process. Escalate priority for sensitive multi-user systems or infrastructure where kernel crashes would affect availability. Current evidence does not support emergency treatment based on exploitation.

Technical view

In stm_register_device(), put_device(&stm->dev) can invoke stm_device_release(), which frees stm. The next vfree(stm) then double-frees the same allocation. The CVE record lists Linux kernel versions and multiple stable kernel commits addressing the issue.

Likely exposure

Exposure is limited to systems running affected Linux kernels with the vulnerable stm class code present. The bundle lists Linux as affected and includes stable kernel fixes, but it does not identify specific distributions beyond a Debian LTS advisory reference.

Exploitation context

The source bundle does not report active exploitation, public exploit availability, KEV listing, or attacker prerequisites. Treat this as a kernel memory-safety issue requiring patch tracking, not as confirmed internet-scale exploitation.

Researcher notes

Key evidence is the upstream description of the double free and stable commit references. The bundle lacks CVSS, CWE, exploitability analysis, and detailed reachability conditions, so validation should focus on kernel version mapping and vendor patch status.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Review Debian LTS guidance where applicable to Debian-based systems.
  • Prioritize kernel updates on systems using affected Linux kernel branches.
  • Check vendor advisories before applying any workaround not named in sources.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, appliances, and containers hosts.
  • Map running kernels to vendor advisories and the referenced stable commits.
  • Confirm patched kernels are booted, not only installed.
  • Track exceptions where reboot or kernel rollout is delayed.
Prepared
Confidence
medium
Sources
11

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-2024-38627 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
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux389b6699a2aa0b457aa69986e9ddf39f3b4030fd, 389b6699a2aa0b457aa69986e9ddf39f3b4030fd, 389b6699a2aa0b457aa69986e9ddf39f3b4030fd, 389b6699a2aa0b457aa69986e9ddf39f3b4030fd, 389b6699a2aa0b457aa69986e9ddf39f3b4030fd, 389b6699a2aa0b457aa69986e9ddf39f3b4030fd, 389b6699a2aa0b457aa69986e9ddf39f3b4030fd, 389b6699a2aa0b457aa69986e9ddf39f3b4030fd, b0351a51ffda593b2b1b35dd0c00a73505edb256unaffected
LinuxLinux4.7, 0, 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, 6.6.33, 6.9.4, 6.10affected
Weakness

CWE details

No CWE listed

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