LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38648: spi: stm32: Check for cfg availability in stm32_spi_probe

In the Linux kernel, the following vulnerability has been resolved: spi: stm32: Check for cfg availability in stm32_spi_probe The stm32_spi_probe function now includes a check to ensure that the pointer returned by of_device_get_match_data is not NULL before accessing its members. This resolves a warning where a potential NULL pointer dereference could occur when accessing cfg->has_device_mode. Before accessing the 'has_device_mode' member, we verify that 'cfg' is not NULL. If 'cfg' is NULL, an error message is logged. This change ensures that the driver does not attempt to access configuration data if it is not available, thus preventing a potential system crash due to a NULL pointer dereference.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-38648 is a Linux kernel flaw in the STM32 SPI driver. A missing configuration pointer check could let the driver dereference NULL during probing, potentially crashing the system. The public sources do not provide CVSS, CWE, exploitability detail, or evidence of active exploitation.

Executive priority

Track and patch through normal kernel maintenance unless STM32-based devices are business-critical or crash-sensitive. Escalate priority for industrial, embedded, or availability-critical systems that rely on the affected driver.

Technical view

In stm32_spi_probe, of_device_get_match_data could return NULL, but the driver accessed cfg->has_device_mode. The resolved change checks cfg before member access and logs an error when configuration data is unavailable, preventing a potential NULL pointer dereference and system crash.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the STM32 SPI driver path. The source bundle lists Linux kernel versions and stable commits, but does not define deployment prerequisites, reachable attack surface, or affected distributions.

Exploitation context

CISA KEV status is false, and the provided sources do not report active exploitation. The bundle describes a potential crash from missing driver configuration data, not privilege escalation, data theft, or remote exploitation.

Researcher notes

The evidence supports a NULL pointer dereference in driver probe handling. Severity is uncertain because the CVE bundle lacks CVSS, CWE, trigger conditions, privilege requirements, and exploit reports. Treat analysis beyond STM32 SPI driver exposure as unconfirmed.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the linked stable fixes.
  • Prioritize Linux devices using STM32 SPI hardware or board support.
  • Check vendor guidance if fixed package versions are not identified.
  • Avoid direct deployment with wrangler-like bypasses; follow normal kernel release channels.

Validation and detection

  • Inventory Linux kernel versions across STM32-based or embedded systems.
  • Confirm whether the STM32 SPI driver is enabled or used.
  • Verify the running kernel includes one of the linked stable fixes.
  • Review vendor advisories for exact fixed distribution package versions.
Prepared
Confidence
medium
Sources
7

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-38648 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
0ADP providers
6Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfee681646fc831b154619ac0261afedcc7e671e7, fee681646fc831b154619ac0261afedcc7e671e7, fee681646fc831b154619ac0261afedcc7e671e7, fee681646fc831b154619ac0261afedcc7e671e7, fee681646fc831b154619ac0261afedcc7e671e7unaffected
LinuxLinux6.6, 0, 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.