Kernel panic via premature GPIO chip removal
Published Sep 24, 2026 · Updated Sep 24, 2026
NULL pointer dereference in Linux bcm2835 pinctrl allows attackers to trigger a kernel panic during driver probe failure. The bcm2835_pinctrl_probe() error path calls gpiochip_remove() before gpiochip_add_data() registers the chip, leaving gpio_chip.gpiodev NULL. Reachability requires devm_pinctrl_register() to fail during BCM2835 driver probing; the resulting NULL dereference can panic the kernel.
Summary
What happened
NULL pointer dereference in Linux bcm2835 pinctrl allows attackers to trigger a kernel panic during driver probe failure. The bcm2835_pinctrl_probe() error path calls gpiochip_remove() before gpiochip_add_data() registers the chip, leaving gpio_chip.gpiodev NULL. Reachability requires devm_pinctrl_register() to fail during BCM2835 driver probing; the resulting NULL dereference can panic the kernel.
The record
- CVE
- CVE-2026-93274
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=266423e60ea1b953fcc0cd97f3dad85857e434d1 <32711f77db0641e57fd96fdc013bf1286b9f2514
- Affected versionversion=266423e60ea1b953fcc0cd97f3dad85857e434d1 <3b978fd0a3092b25561ac26bc1a87149fa981ddc
- Affected versionversion=266423e60ea1b953fcc0cd97f3dad85857e434d1 <68ea6dd23b732081826c36033835468383487864
- Affected versionversion=266423e60ea1b953fcc0cd97f3dad85857e434d1 <727f043d699ab0d5d87122c2177f2b45fbe58d35
- Affected versionversion=266423e60ea1b953fcc0cd97f3dad85857e434d1 <b8535f5c77cc61352d02a0c038a280127a8b8208
- Affected versionversion=266423e60ea1b953fcc0cd97f3dad85857e434d1 <dd6b1919e41d1260259c4505777be565fb3a7efd
- Affected versionversion=5.10.89 <5.10.270
- Affected versionversion=5.15.12 <5.15.221
- Affected versionversion=5.16
- Affected versionversion=5.4.175 <5.5
- Affected versionversion=75278f1aff5e14c904d3503c6f836c42a7afb441
- Affected versionversion=79c6d4fa1be1fd0819c50ebb4dee101bbbc4d20e <f494cfc254cd509d7cbc44b843e0a6602a520a33
- Affected versionversion=ba696b470839d70c6b8290c1f798bac7fb2a584c <d428863ca8baa4e9eaf781266ac219b017dcf277
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started