Linux Kernel up to 6.12.39/6.15.7 iio st_sensors_power_enable uninitialized pointer

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.9$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 6.12.39/6.15.7. The affected element is the function st_sensors_power_enable of the component iio. Performing a manipulation results in uninitialized pointer. This vulnerability was named CVE-2025-38531. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.12.39/6.15.7. This affects the function st_sensors_power_enable of the component iio. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. CWE is classifying the issue as CWE-824. The product accesses or uses a pointer that has not been initialized. The impact remains unknown. The summary by CVE is:

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]

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-38531 since 04/16/2025. The exploitability is told to be difficult. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 265749 (SUSE SLED15 / SLES15 Security Update : kernel (SUSE-SU-2025:03290-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.40 or 6.15.8 eliminates this vulnerability. Applying the patch 610615c9668037e3eca11132063b93b2d945af13/3297a9016a45144883ec990bd4bd5b1d79cafb46/9f92e93e257b33e73622640a9205f8642ec16ddd is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (265749) and CERT Bund (WID-SEC-2025-1858). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Dell Avamar
  • Open Source Linux Kernel
  • Dell NetWorker
  • Dell Secure Connect Gateway
  • IBM QRadar SIEM
  • IBM Security Verify Access

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Uninitialized pointer
CWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 265749
Nessus Name: SUSE SLED15 / SLES15 Security Update : kernel (SUSE-SU-2025:03290-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.40/6.15.8
Patch: 610615c9668037e3eca11132063b93b2d945af13/3297a9016a45144883ec990bd4bd5b1d79cafb46/9f92e93e257b33e73622640a9205f8642ec16ddd

Timelineinfo

04/16/2025 CVE reserved
08/16/2025 +122 days Advisory disclosed
08/16/2025 +0 days VulDB entry created
01/30/2026 +167 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38531 (🔒)
GCVE (CVE): GCVE-0-2025-38531
GCVE (VulDB): GCVE-100-320403
CERT Bund: WID-SEC-2025-1858 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 08/16/2025 18:03
Updated: 01/30/2026 18:44
Changes: 08/16/2025 18:03 (58), 09/24/2025 05:28 (2), 09/28/2025 08:53 (7), 10/03/2025 13:23 (1), 10/12/2025 18:53 (1), 11/01/2025 19:49 (1), 11/19/2025 01:37 (12), 01/30/2026 18:44 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!