0.0
NA
CVE-2025-40030
pinctrl: check the return value of pinmux_ops::get_function_name()
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.

INFO

Published Date :

Oct. 28, 2025, 12:15 p.m.

Last Modified :

Oct. 28, 2025, 12:15 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2025-40030 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
Solution
Ensure pinmux_ops::get_function_name() return values are checked to prevent NULL pointer dereferences.
  • Update the Linux kernel code.
  • Check return values from get_function_name().
  • Avoid dereferencing NULL pointers in strcmp().
  • Apply patch to the pinctrl subsystem.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-40030 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-40030 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-40030 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2025-40030 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 28, 2025

    Action Type Old Value New Value
    Added 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.
    Added Reference https://git.kernel.org/stable/c/1a2ea887a5cd7d47bab599f733d89444df018b1a
    Added Reference https://git.kernel.org/stable/c/4002ee98c022d671ecc1e4a84029e9ae7d8a5603
    Added Reference https://git.kernel.org/stable/c/688c688e0bf55824f4a38f8c2180046f089a3e3b
    Added Reference https://git.kernel.org/stable/c/b7e0535060a60cc99eafc19cc665d979714cd73a
    Added Reference https://git.kernel.org/stable/c/ba7f7c2b2b3261e7def67018c38c69b626e0e66e
    Added Reference https://git.kernel.org/stable/c/d77ef2f621cd1d605372c4c6ce667c496f6990c3
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.