CVE-2024-26866

What the bug is

fsl_lpspi_probe() is allocating/disposing memory manually with spi_alloc_host()/spi_alloc_target(), but uses devm_spi_register_controller(). In case of error after the latter call the memory will be explicitly freed in the probe function by spi_controller_put() call, but used afterwards by "devm" management outside probe() (spi_unregister_controller() <- devm_spi_unregister() below). Unable to handle kernel NULL pointer dereference at virtual address 0000000000000070 ... Call trace: kernfs_find_ns kernfs_find_and_get_ns sysfs_remove_group sysfs_remove_groups device_remove_attrs device_del spi_unregister_controller devm_spi_unregister release_nodes devres_release_all really_probe driver_probe_device __device_attach_driver bus_for_each_drv __device_attach device_initial_probe bus_probe_device deferred_probe_work_func process_one_work worker_thread kthread ret_from_fork

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/spi/spi-fsl-lpspi.c

What this is

FREESCALE IMX LPSPI DRIVERMAINTAINERS section matched on drivers/spi/spi-fsl-lpspi.c · linux-spi@vger.kernel.org · Maintained

Kernel module

none to look for. The file would have gone into spi_fsl_lpspi, and Debian does not compile it into that module, so finding spi_fsl_lpspi in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_SPI|CONFIG_SPI_FSL_LPSPI' /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.

Show whether Debian builds this, per release

Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

• bookworm, trixie, forky, sidn

n

not enabled on any flavour - this release does not build the code

Build switches

CONFIG_SPI, CONFIG_SPI_FSL_LPSPI

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

2024-04-17 (3 years ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.22%, higher than 11.2% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/spi

Upstream fixes

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

Introduced	Fixed in	Commit
4.10	6.6.23	da83ed350e46
4.10	6.7.11	1543418e8278
4.10	6.8.2	996ce839606a
4.10	6.9	2ae0ab0143fc