Bug 2406728 (CVE-2025-40030) - CVE-2025-40030 kernel: pinctrl: check the return value of pinmux_ops::get_function_name()
Summary: CVE-2025-40030 kernel: pinctrl: check the return value of pinmux_ops::get_fun...
Keywords:
Status: NEW
Alias: CVE-2025-40030
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-28 12:02 UTC by OSIDB Bzimport
Modified: 2025-10-28 19:31 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-10-28 12:02:13 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.