linux-cve-announce - CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function

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: <2025102810-CVE-2025-40030-b395@gregkh>
Date: Tue, 28 Oct 2025 12:48:07 +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-40030: pinctrl: check the return value of pinmux_ops::get_function_name()

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

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

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

pinctrl: check the return value of pinmux_ops::get_function_name()

While the API contract in docs doesn't specify it explicitly, the
generic implementation of the get_function_name() callback from struct
pinmux_ops - pinmux_generic_get_function_name() - can fail and return
NULL. This is already checked in pinmux_check_ops() so add a similar
check in pinmux_func_name_to_selector() instead of passing the returned
pointer right down to strcmp() where the NULL can get dereferenced. This
is normal operation when adding new pinfunctions.

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


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

	Fixed in 5.15.195 with commit d77ef2f621cd1d605372c4c6ce667c496f6990c3
	Fixed in 6.1.156 with commit ba7f7c2b2b3261e7def67018c38c69b626e0e66e
	Fixed in 6.6.112 with commit 1a2ea887a5cd7d47bab599f733d89444df018b1a
	Fixed in 6.12.53 with commit 688c688e0bf55824f4a38f8c2180046f089a3e3b
	Fixed in 6.17.3 with commit b7e0535060a60cc99eafc19cc665d979714cd73a
	Fixed in 6.18-rc1 with commit 4002ee98c022d671ecc1e4a84029e9ae7d8a5603

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-40030
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/pinctrl/pinmux.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/d77ef2f621cd1d605372c4c6ce667c496f6990c3
	https://git.kernel.org/stable/c/ba7f7c2b2b3261e7def67018c38c69b626e0e66e
	https://git.kernel.org/stable/c/1a2ea887a5cd7d47bab599f733d89444df018b1a
	https://git.kernel.org/stable/c/688c688e0bf55824f4a38f8c2180046f089a3e3b
	https://git.kernel.org/stable/c/b7e0535060a60cc99eafc19cc665d979714cd73a
	https://git.kernel.org/stable/c/4002ee98c022d671ecc1e4a84029e9ae7d8a5603