CVE-2026-93274 json
pinctrl: bcm2835: Don't remove an unregistered GPIO chip
published 2026-09-24 45 d ago modified 2026-10-19 21 d ago also EUVD-2026-86146
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- Linux Linux 5.5, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-93274
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-93274
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default Linux Micro 6.0 6.4.0-159998.55.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.90.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.90.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
suse advisories SUSE-SU-2026:24550-1SUSE-SU-2026:5091-1
- kernel-source openSUSE Tumbleweed 7.2.8-1.1
opensuse advisories openSUSE-SU-2026:11893-1
- git.kernel.org/stable/c/d428863ca8baa4e9eaf781266ac219b017dcf277 commit
- git.kernel.org/stable/c/f494cfc254cd509d7cbc44b843e0a6602a520a33 commit
- git.kernel.org/stable/c/dd6b1919e41d1260259c4505777be565fb3a7efd commit
- git.kernel.org/stable/c/3b978fd0a3092b25561ac26bc1a87149fa981ddc commit
- git.kernel.org/stable/c/b8535f5c77cc61352d02a0c038a280127a8b8208 commit
- git.kernel.org/stable/c/68ea6dd23b732081826c36033835468383487864 commit
- git.kernel.org/stable/c/727f043d699ab0d5d87122c2177f2b45fbe58d35 commit
- git.kernel.org/stable/c/32711f77db0641e57fd96fdc013bf1286b9f2514 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-93274 updated cvss 5.5
kernel: pinctrl: bcm2835: Don't remove an unregistered GPIO chip
-
Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/d428863ca8baa4e9eaf781266ac219b017dcf277
- git.kernel.org /stable/c/f494cfc254cd509d7cbc44b843e0a6602a520a33
- git.kernel.org /stable/c/dd6b1919e41d1260259c4505777be565fb3a7efd
- git.kernel.org /stable/c/3b978fd0a3092b25561ac26bc1a87149fa981ddc
- git.kernel.org /stable/c/b8535f5c77cc61352d02a0c038a280127a8b8208
- git.kernel.org /stable/c/68ea6dd23b732081826c36033835468383487864
- git.kernel.org /stable/c/727f043d699ab0d5d87122c2177f2b45fbe58d35
- git.kernel.org /stable/c/32711f77db0641e57fd96fdc013bf1286b9f2514
Sources
- CVE List CVE-2026-93274
- NVD CVE-2026-93274
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.