linux-cve-announce - CVE-2025-38648: spi: stm32: Check for cfg availability in stm32_spi

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: <2025082236-CVE-2025-38648-adcc@gregkh>
Date: Fri, 22 Aug 2025 18:00:56 +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-38648: spi: stm32: Check for cfg availability in stm32_spi_probe

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

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

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

spi: stm32: Check for cfg availability in stm32_spi_probe

The stm32_spi_probe function now includes a check to ensure that the
pointer returned by of_device_get_match_data is not NULL before
accessing its members. This resolves a warning where a potential NULL
pointer dereference could occur when accessing cfg->has_device_mode.

Before accessing the 'has_device_mode' member, we verify that 'cfg' is
not NULL. If 'cfg' is NULL, an error message is logged.

This change ensures that the driver does not attempt to access
configuration data if it is not available, thus preventing a potential
system crash due to a NULL pointer dereference.

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


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

	Issue introduced in 6.6 with commit fee681646fc831b154619ac0261afedcc7e671e7 and fixed in 6.6.102 with commit 6031a54f4eac921efe6122a561d44df89b37f2d4
	Issue introduced in 6.6 with commit fee681646fc831b154619ac0261afedcc7e671e7 and fixed in 6.12.42 with commit a7645815edf4478f3258bb0db95a08986a77f5c0
	Issue introduced in 6.6 with commit fee681646fc831b154619ac0261afedcc7e671e7 and fixed in 6.15.10 with commit 3a571a8d52272cc26858ab1bc83d0f66e5dee938
	Issue introduced in 6.6 with commit fee681646fc831b154619ac0261afedcc7e671e7 and fixed in 6.16.1 with commit cc063d23ad80ef7d201c41b2716b1bae7c662cf9
	Issue introduced in 6.6 with commit fee681646fc831b154619ac0261afedcc7e671e7 and fixed in 6.17-rc1 with commit 21f1c800f6620e43f31dfd76709dbac8ebaa5a16

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-38648
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/spi/spi-stm32.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/6031a54f4eac921efe6122a561d44df89b37f2d4
	https://git.kernel.org/stable/c/a7645815edf4478f3258bb0db95a08986a77f5c0
	https://git.kernel.org/stable/c/3a571a8d52272cc26858ab1bc83d0f66e5dee938
	https://git.kernel.org/stable/c/cc063d23ad80ef7d201c41b2716b1bae7c662cf9
	https://git.kernel.org/stable/c/21f1c800f6620e43f31dfd76709dbac8ebaa5a16