CVE-2026-93274: Linux kernel · pinctrl: bcm2835: Don't remove an unregistered GPIO chip
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f494cfc254cd509d7cbc44b843e0a6602a520a33 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f494cfc254cd509d7cbc44b843e0a6602a520a33, dd6b1919e41d1260259c4505777be565fb3a7efd, d428863ca8baa4e9eaf781266ac219b017dcf277 +8
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This issue has been fixed in Linux kernel versions 5.10.270, 5.15.221, 5.5, and 5.16. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are required as the fix removes the problematic function call.
Description
A vulnerability in the Linux kernel's bcm2835 pinctrl driver could cause a kernel panic due to a null pointer dereference when the GPIO chip removal function is called on an unregistered chip. This occurs if devm_pinctrl_register() fails and gpiochip_remove() is called before the GPIO chip is registered. The issue has been fixed by removing the unnecessary call to gpiochip_remove().
References
- git.kernel.org/stable/c/d428863ca8baa4e9eaf781266ac219b017dcf277 (opens in a new tab)
- git.kernel.org/stable/c/f494cfc254cd509d7cbc44b843e0a6602a520a33 (opens in a new tab)
- git.kernel.org/stable/c/dd6b1919e41d1260259c4505777be565fb3a7efd (opens in a new tab)
- git.kernel.org/stable/c/3b978fd0a3092b25561ac26bc1a87149fa981ddc (opens in a new tab)
- git.kernel.org/stable/c/b8535f5c77cc61352d02a0c038a280127a8b8208 (opens in a new tab)
- git.kernel.org/stable/c/68ea6dd23b732081826c36033835468383487864 (opens in a new tab)
- git.kernel.org/stable/c/727f043d699ab0d5d87122c2177f2b45fbe58d35 (opens in a new tab)
- git.kernel.org/stable/c/32711f77db0641e57fd96fdc013bf1286b9f2514 (opens in a new tab)