linux-cve-announce - CVE-2025-71198: iio: imu: st_lsm6dsx: fix iio_chan

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2026020412-CVE-2025-71198-3572@gregkh>
Date: Wed,  4 Feb 2026 17:14:13 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-71198: iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection

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

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

In the Linux kernel, the following vulnerability has been resolved:

iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection

The st_lsm6dsx_acc_channels array of struct iio_chan_spec has a non-NULL
event_spec field, indicating support for IIO events. However, event
detection is not supported for all sensors, and if userspace tries to
configure accelerometer wakeup events on a sensor device that does not
support them (e.g. LSM6DS0), st_lsm6dsx_write_event() dereferences a NULL
pointer when trying to write to the wakeup register.
Define an additional struct iio_chan_spec array whose members have a NULL
event_spec field, and use this array instead of st_lsm6dsx_acc_channels for
sensors without event detection capability.

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


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

	Issue introduced in 5.5 with commit b5969abfa8b8ed43ebd93479d394f664bd4a5a87 and fixed in 6.6.122 with commit 7673167fac9323110973a3300637adba7d45de3a
	Issue introduced in 5.5 with commit b5969abfa8b8ed43ebd93479d394f664bd4a5a87 and fixed in 6.12.68 with commit 4d60ffcdedfe2cdb68a1cde19bb292bc67451629
	Issue introduced in 5.5 with commit b5969abfa8b8ed43ebd93479d394f664bd4a5a87 and fixed in 6.18.8 with commit 81ed6e42d6e555dd978c9dd5e3f7c20cb121221b
	Issue introduced in 5.5 with commit b5969abfa8b8ed43ebd93479d394f664bd4a5a87 and fixed in 6.19-rc7 with commit c34e2e2d67b3bb8d5a6d09b0d6dac845cdd13fb3

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-71198
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/imu/st_lsm6dsx/st_lsm6dsx_core.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/7673167fac9323110973a3300637adba7d45de3a
	https://git.kernel.org/stable/c/4d60ffcdedfe2cdb68a1cde19bb292bc67451629
	https://git.kernel.org/stable/c/81ed6e42d6e555dd978c9dd5e3f7c20cb121221b
	https://git.kernel.org/stable/c/c34e2e2d67b3bb8d5a6d09b0d6dac845cdd13fb3