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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025081655-CVE-2025-38531-abbc@gregkh>
Date: Sat, 16 Aug 2025 13:14:02 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38531: iio: common: st_sensors: Fix use of uninitialize device structs

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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]

The Linux kernel CVE team has assigned CVE-2025-38531 to this issue.


Affected and fixed versions
===========================

	Fixed in 6.12.40 with commit 610615c9668037e3eca11132063b93b2d945af13
	Fixed in 6.15.8 with commit 3297a9016a45144883ec990bd4bd5b1d79cafb46
	Fixed in 6.16 with commit 9f92e93e257b33e73622640a9205f8642ec16ddd

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-38531
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/iio/accel/st_accel_core.c
	drivers/iio/common/st_sensors/st_sensors_core.c
	drivers/iio/common/st_sensors/st_sensors_trigger.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/610615c9668037e3eca11132063b93b2d945af13
	https://git.kernel.org/stable/c/3297a9016a45144883ec990bd4bd5b1d79cafb46
	https://git.kernel.org/stable/c/9f92e93e257b33e73622640a9205f8642ec16ddd