LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38531: iio: common: st_sensors: Fix use of uninitialize device structs

In the Linux kernel, the following vulnerability has been resolved: iio: common: st_sensors: Fix use of uninitialize device structs Throughout the various probe functions &indio_dev->dev is used before it is initialized. This caused a kernel panic in st_sensors_power_enable() when the call to devm_regulator_bulk_get_enable() fails and then calls dev_err_probe() with the uninitialized device. This seems to only cause a panic with dev_err_probe(), dev_err(), dev_warn() and dev_info() don't seem to cause a panic, but are fixed as well. The issue is reported and traced here: [1]

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can trigger a kernel panic during startup or device probing for ST sensor drivers when regulator setup fails. The source describes an availability issue, not data theft or remote code execution. Public severity scoring is not provided, so business urgency depends on whether affected kernels and relevant sensor drivers are present.

Executive priority

Treat this as a targeted availability risk for relevant Linux fleets, especially embedded or hardware-specific deployments using ST sensors. It should be patched through normal kernel maintenance unless local evidence shows crashes or dependency on affected drivers, which would raise priority.

Technical view

In Linux IIO st_sensors probe paths, &indio_dev->dev was used before initialization. When devm_regulator_bulk_get_enable() failed, dev_err_probe() could dereference the uninitialized device structure and panic the kernel. The vulnerability is marked resolved in stable kernel commits, but the bundle provides no CVSS, CWE, or exploit mechanics.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the IIO st_sensors code path present. The bundle lists Linux kernel ranges including 5.16, 6.6.136, 6.12.40, 6.15.8, and 6.16, but does not identify distributions or downstream package versions.

Exploitation context

CISA KEV is false, and the provided sources do not report active exploitation. The described failure requires the vulnerable probe path and a regulator setup failure condition, causing a panic through logging/error handling rather than a documented attacker-controlled exploit path.

Researcher notes

The source evidence is narrow: a kernel panic from premature use of &indio_dev->dev in st_sensors probe error handling. No CVSS, CWE, privilege boundary, or reproducible exploit details are provided. Validation should focus on kernel lineage, driver presence, and whether regulator failure paths are reachable.

Mitigation direction

  • Check vendor or distribution kernel advisories for CVE-2025-38531 fixes.
  • Update to a kernel build containing the referenced stable fixes when available.
  • Prioritize systems using ST sensor IIO drivers or affected hardware paths.
  • Track vendor guidance if fixed downstream package names are not yet clear.

Validation and detection

  • Inventory Linux kernel versions against the affected versions in the CVE record.
  • Confirm whether st_sensors IIO drivers are enabled or used in deployed builds.
  • Review kernel changelogs for the referenced stable commit IDs.
  • Check crash telemetry for panics in st_sensors_power_enable or related probe paths.
Prepared
Confidence
medium
Sources
6

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-38531 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
5Source 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
LinuxLinux4dff754876959b3f3b354800089bc8aaa3ec1d95, 4dff754876959b3f3b354800089bc8aaa3ec1d95, 4dff754876959b3f3b354800089bc8aaa3ec1d95, 4dff754876959b3f3b354800089bc8aaa3ec1d95unaffected
LinuxLinux5.16, 0, 6.6.136, 6.12.40, 6.15.8, 6.16affected
Weakness

CWE details

No CWE listed

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