CVE-2025-40030

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

N/A
Published: October 28, 2025 at 11:48 AM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19f913cfce4ee49a3382a9ff95696f49a46e56e974
Vendor states this is fixed in 1a2ea887a5cd7d47bab599f733d89444df018b1a (fixed)
Vendor states this is fixed in 1a7fc8fed2bb2e113604fde7a45432ace2056b97 (fixed)
Vendor states this is fixed in 4002ee98c022d671ecc1e4a84029e9ae7d8a5603 (fixed)
Vendor states this is fixed in 688c688e0bf55824f4a38f8c2180046f089a3e3b (fixed)
Vendor states this is fixed in b7e0535060a60cc99eafc19cc665d979714cd73a (fixed)
Vendor states this is fixed in ba7f7c2b2b3261e7def67018c38c69b626e0e66e (fixed)
Vendor states this is fixed in d77ef2f621cd1d605372c4c6ce667c496f6990c3 (fixed)
Vendor states this is fixed in e7265dc4c670b89611bcf5fe33acf99bc0aa294f (fixed)
Vendor states this is fixed in 4.19 (unaffected)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.195 (unaffected)
Vendor states this is fixed in 5.4.301 (unaffected)
Vendor states this is fixed in 6.1.156 (unaffected)
Vendor states this is fixed in 6.12.53 (unaffected)
Vendor states this is fixed in 6.17.3 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.112 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card