Strix
26.1K

CVE-2025-40030

UnknownEPSS 0.21%

Last modified

CVE-2025-40030 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.21%

10.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= f913cfce4ee49a3382a9ff95696f49a46e56e974, < 1a7fc8fed2bb2e113604fde7a45432ace2056b97; >= f913cfce4ee49a3382a9ff95696f49a46e56e974, < e7265dc4c670b89611bcf5fe33acf99bc0aa294f; >= f913cfce4ee49a3382a9ff95696f49a46e56e974, < d77ef2f621cd1d605372c4c6ce667c496f6990c3; >= f913cfce4ee49a3382a9ff95696f49a46e56e974, < ba7f7c2b2b3261e7def67018c38c69b626e0e66e; >= f913cfce4ee49a3382a9ff95696f49a46e56e974, < 1a2ea887a5cd7d47bab599f733d89444df018b1a; >= f913cfce4ee49a3382a9ff95696f49a46e56e974, < 688c688e0bf55824f4a38f8c2180046f089a3e3b; >= f913cfce4ee49a3382a9ff95696f49a46e56e974, < b7e0535060a60cc99eafc19cc665d979714cd73a; >= f913cfce4ee49a3382a9ff95696f49a46e56e974, < 4002ee98c022d671ecc1e4a84029e9ae7d8a5603
LinuxLinux4.19

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-40030?
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.
How severe is CVE-2025-40030?
Severity scoring for CVE-2025-40030 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2025-40030?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

View all 2025CVEs →

Are you affected by CVE-2025-40030?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST