# CVE-2026-90340: pinctrl: generic: free maps on pinctrl_generic_to_map() failure

> A memory leak in the Linux kernel pinctrl subsystem allows local attackers to cause denial of service by triggering error paths that fail to free allocated memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-9qrw-29c6-r5gv, UBUNTU-CVE-2026-90340

## What is CVE-2026-90340?

CVE-2026-90340 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. 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: generic: free maps on pinctrl_generic_to_map() failure

pinctrl_generic_to_map() parses DT configuration and allocates pinctrl
maps via pinctrl_utils_reserve_map().

If subsequent steps (such as pinctrl_utils_add_map_mux(),
pinctrl_generic_add_group(), pinconf_generic_parse_dt_config(), or
pinctrl_utils_add_map_configs()) return an error, *maps may contain
partially allocated map entries. Returning the error directly without
freeing *maps leaks the allocated mapping memory across all drivers
that rely on pinctrl_generic_to_map().

Fix this by calling pinctrl_utils_free_map() and resetting *maps,
*num_maps, and *num_reserved_maps in the error path of
pinctrl_generic_to_map().

## Which versions are affected by CVE-2026-90340?


## How do I fix CVE-2026-90340?

Apply the vendor's patch.

## Is CVE-2026-90340 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90340 and fix it if it is affected.

What it is: CVE-2026-90340 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. 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-2026-90340 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-2026-90340/ (Markdown: https://insights.sbomify.com/CVE-2026-90340/index.md)
```

## Sources

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

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