CVE-2025-71198

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c

What this is

ST LSM6DSx IMU IIO DRIVERMAINTAINERS section matched on drivers/iio/imu/st_lsm6dsx/ · linux-iio@vger.kernel.org · Maintained

Kernel module

st_lsm6dsx

Check it on the machine

grep -wE 'CONFIG_IIO|CONFIG_IIO_ST_LSM6DSX' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w st_lsm6dsx

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

• bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64
• trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x

M

a module where it is built at all; some flavours do not build it

Build switches

CONFIG_IIO, CONFIG_IIO_ST_LSM6DSX

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-02-04 (8 months ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.20%, higher than 8.7% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/iio

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
5.5	6.6.122	7673167fac93
5.5	6.12.68	4d60ffcdedfe
5.5	6.18.8	81ed6e42d6e5
5.5	6.19	c34e2e2d67b3

Debian advisories