LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-40030 is a Linux kernel reliability flaw in pin control handling. A kernel callback can legitimately return NULL, but one code path compared it as a string, risking a NULL pointer dereference. The public record does not provide CVSS, impact scope, or exploitation evidence.

Executive priority

Treat as a kernel maintenance item until severity is clarified. There is no exploitation evidence in the supplied sources, but kernel crashes can affect availability on exposed or embedded Linux platforms. Prioritize normal patch cycles and higher urgency for custom kernels or hardware-dependent pinctrl usage.

Technical view

The flaw is in pinctrl/pinmux logic: pinmux_func_name_to_selector() failed to check pinmux_ops::get_function_name() before passing the result to strcmp(). The fix adds a NULL check similar to pinmux_check_ops(). The source describes this as possible during normal operation when adding new pinfunctions.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream kernels carrying the vulnerable pinctrl code. The source bundle lists affected Linux versions including 4.19, 5.4.301, 5.10.246, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3, and 6.18.

Exploitation context

No active exploitation is indicated. The CVE is not marked KEV, and the provided sources do not describe public exploitation. Available evidence supports a potential kernel NULL dereference condition, not a confirmed privilege escalation or remote attack path.

Researcher notes

Evidence is narrow: the CVE description and stable commits identify the bug class and fix pattern, but not attack preconditions, reachable drivers, CVSS, or real-world exploitation. Analysis should focus on affected kernel trees, downstream backports, and whether local hardware or driver paths reach pinmux_func_name_to_selector().

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Use distribution vendor kernel advisories for packaged kernels.
  • Prioritize systems using affected pinctrl or pinmux drivers.
  • Avoid custom kernel builds missing the upstream NULL-check patch.
  • Track downstream backports if exact upstream versions differ.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Confirm vendor kernel packages include the referenced stable commits.
  • Review custom kernel trees for the added NULL check.
  • Check whether affected pinctrl code is compiled and used.
  • Monitor kernel logs for related NULL dereference crashes.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-40030 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf913cfce4ee49a3382a9ff95696f49a46e56e974, f913cfce4ee49a3382a9ff95696f49a46e56e974, f913cfce4ee49a3382a9ff95696f49a46e56e974, f913cfce4ee49a3382a9ff95696f49a46e56e974, f913cfce4ee49a3382a9ff95696f49a46e56e974, f913cfce4ee49a3382a9ff95696f49a46e56e974, f913cfce4ee49a3382a9ff95696f49a46e56e974, f913cfce4ee49a3382a9ff95696f49a46e56e974unaffected
LinuxLinux4.19, 0, 5.4.301, 5.10.246, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3, 6.18affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.