CVE-2026-93274
pinctrl: bcm2835: Don't remove an unregistered GPIO chip
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
INFO
Published Date :
Sept. 24, 2026, 4:17 p.m.
Last Modified :
Sept. 24, 2026, 4:17 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Remove the unnecessary gpiochip_remove() function call.
- Ensure no GPIO cleanup occurs if chip is not registered.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-93274.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-93274 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-93274
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-93274 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-93274 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 24, 2026
Action Type Old Value New Value Added 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 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/93xxx/CVE-2026-93274.json">CVE-2026-93274</a> Added Reference https://git.kernel.org/stable/c/32711f77db0641e57fd96fdc013bf1286b9f2514 Added Reference https://git.kernel.org/stable/c/3b978fd0a3092b25561ac26bc1a87149fa981ddc Added Reference https://git.kernel.org/stable/c/68ea6dd23b732081826c36033835468383487864 Added Reference https://git.kernel.org/stable/c/727f043d699ab0d5d87122c2177f2b45fbe58d35 Added Reference https://git.kernel.org/stable/c/b8535f5c77cc61352d02a0c038a280127a8b8208 Added Reference https://git.kernel.org/stable/c/d428863ca8baa4e9eaf781266ac219b017dcf277 Added Reference https://git.kernel.org/stable/c/dd6b1919e41d1260259c4505777be565fb3a7efd Added Reference https://git.kernel.org/stable/c/f494cfc254cd509d7cbc44b843e0a6602a520a33