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

> A null pointer dereference in the Linux kernel pinctrl subsystem allows local attackers to cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-68849, BELL-CVE-2025-40030, DEBIAN-CVE-2025-40030, GHSA-jq6c-xqjw-rcrp, ROOT-OS-DEBIAN-11-CVE-2025-40030, ROOT-OS-DEBIAN-12-CVE-2025-40030, ROOT-OS-DEBIAN-13-CVE-2025-40030, ROOT-OS-UBUNTU-2204-CVE-2025-40030, ROOT-OS-UBUNTU-2404-CVE-2025-40030, UBUNTU-CVE-2025-40030

## What is CVE-2025-40030?

CVE-2025-40030 is a vulnerability in Linux, published on 28 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-40030?


## How do I fix CVE-2025-40030?

Apply the vendor's patch.

## Is CVE-2025-40030 being exploited?

There is no known exploitation of CVE-2025-40030 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40030 and fix it if it is affected.

What it is: CVE-2025-40030 is a vulnerability in Linux, published on 28 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40030 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40030/ (Markdown: https://insights.sbomify.com/CVE-2025-40030/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40030
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40030
- OSV: https://osv.dev/vulnerability/CVE-2025-40030

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40030/
Summaries are generated and may contain mistakes; the official description above is the record.