CVE-2026-93274 — pinctrl: bcm2835: Don't remove an unregistered GPIO chip
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
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ ba696b470839d70c6b8290c1f798bac7fb2a584c and < d428863ca8baa4e9eaf781266ac219b017dcf277≥ 79c6d4fa1be1fd0819c50ebb4dee101bbbc4d20e and < f494cfc254cd509d7cbc44b843e0a6602a520a33≥ 266423e60ea1b953fcc0cd97f3dad85857e434d1 and < dd6b1919e41d1260259c4505777be565fb3a7efd≥ 266423e60ea1b953fcc0cd97f3dad85857e434d1 and < 3b978fd0a3092b25561ac26bc1a87149fa981ddc≥ 266423e60ea1b953fcc0cd97f3dad85857e434d1 and < b8535f5c77cc61352d02a0c038a280127a8b8208≥ 266423e60ea1b953fcc0cd97f3dad85857e434d1 and < 68ea6dd23b732081826c36033835468383487864≥ 266423e60ea1b953fcc0cd97f3dad85857e434d1 and < 727f043d699ab0d5d87122c2177f2b45fbe58d35≥ 266423e60ea1b953fcc0cd97f3dad85857e434d1 and < 32711f77db0641e57fd96fdc013bf1286b9f2514 and 5 moreversion 75278f1aff5e14c904d3503c6f836c42a7afb441≥ 5.10.89 and < 5.10.270≥ 5.15.12 and < 5.15.221≥ 5.4.175 and < 5.5version 5.16 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/d428863ca8baa4e9eaf781266ac219b017dcf277
- git.kernel.org/stable/c/727f043d699ab0d5d87122c2177f2b45fbe58d35
- git.kernel.org/stable/c/3b978fd0a3092b25561ac26bc1a87149fa981ddc
- git.kernel.org/stable/c/dd6b1919e41d1260259c4505777be565fb3a7efd
- git.kernel.org/stable/c/f494cfc254cd509d7cbc44b843e0a6602a520a33
- git.kernel.org/stable/c/68ea6dd23b732081826c36033835468383487864
- git.kernel.org/stable/c/32711f77db0641e57fd96fdc013bf1286b9f2514
- git.kernel.org/stable/c/b8535f5c77cc61352d02a0c038a280127a8b8208
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 2d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 2d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93274 is "pinctrl: bcm2835: Don't remove an unregistered GPIO chip", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.