# CVE-2026-93274: pinctrl: bcm2835: Don't remove an unregistered GPIO chip

> A null pointer dereference in the BCM2835 pinctrl driver can cause a kernel panic if GPIO registration fails, leading to denial of service.

- **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:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93274, DEBIAN-CVE-2026-93274, GHSA-6v4f-r38f-j6j4, UBUNTU-CVE-2026-93274

## What is CVE-2026-93274?

CVE-2026-93274 is a vulnerability in Linux, published on 24 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: bcm2835: Don't remove an unregistered GPIO chip

If the devm_pinctrl_register() function fails,
bcm2835_pinctrl_probe() calls gpiochip_remove()
before gpiochip_add_data() has registered the GPIO chip.

This means that upon failure the gpio_chip.gpiodev
 is NULL resulting in a null pointer dereference
inside the gpiochip_remove() function.

Remove the unnecessary function call to gpiochip_remove().
No GPIO cleanup is required because the GPIO chip
has not yet been registered. Without this change there
is potential for a kernel panic upon registration failure

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


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

Apply the vendor's patch.

## Is CVE-2026-93274 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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