CVE-2026-93274
Published Sep 24, 2026
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
Is your site exposed to CVE-2026-93274?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/32711f77db0641e57fd96fdc013bf1286b9f2514
https://git.kernel.org/stable/c/3b978fd0a3092b25561ac26bc1a87149fa981ddc
https://git.kernel.org/stable/c/68ea6dd23b732081826c36033835468383487864
https://git.kernel.org/stable/c/727f043d699ab0d5d87122c2177f2b45fbe58d35
https://git.kernel.org/stable/c/b8535f5c77cc61352d02a0c038a280127a8b8208
https://git.kernel.org/stable/c/d428863ca8baa4e9eaf781266ac219b017dcf277
https://git.kernel.org/stable/c/dd6b1919e41d1260259c4505777be565fb3a7efd
https://git.kernel.org/stable/c/f494cfc254cd509d7cbc44b843e0a6602a520a33
Frequently Asked Questions
What is CVE-2026-93274? +
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
How do I check if I'm vulnerable to CVE-2026-93274? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.