CVE-2026-93274

pinctrl: bcm2835: Don't remove an unregistered GPIO chip

N/A
Published: September 24, 2026 at 03:52 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

266423e60ea1b953fcc0cd97f3dad85857e434d15.10.895.15.125.165.4.17575278f1aff5e14c904d3503c6f836c42a7afb44179c6d4fa1be1fd0819c50ebb4dee101bbbc4d20eba696b470839d70c6b8290c1f798bac7fb2a584c
Vendor states this is fixed in 32711f77db0641e57fd96fdc013bf1286b9f2514 (fixed)
Vendor states this is fixed in 3b978fd0a3092b25561ac26bc1a87149fa981ddc (fixed)
Vendor states this is fixed in 68ea6dd23b732081826c36033835468383487864 (fixed)
Vendor states this is fixed in 727f043d699ab0d5d87122c2177f2b45fbe58d35 (fixed)
Vendor states this is fixed in b8535f5c77cc61352d02a0c038a280127a8b8208 (fixed)
Vendor states this is fixed in d428863ca8baa4e9eaf781266ac219b017dcf277 (fixed)
Vendor states this is fixed in dd6b1919e41d1260259c4505777be565fb3a7efd (fixed)
Vendor states this is fixed in f494cfc254cd509d7cbc44b843e0a6602a520a33 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.16 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card