Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-93274 Overview
CVE-2026-93274 is a null pointer dereference vulnerability in the Linux kernel's pinctrl: bcm2835 driver. The flaw affects the Broadcom BCM2835 pin controller used in Raspberry Pi hardware and related platforms. When devm_pinctrl_register() fails during probe, bcm2835_pinctrl_probe() invokes gpiochip_remove() before gpiochip_add_data() has registered the GPIO chip. The gpio_chip.gpiodev field is still NULL at that point, leading to a kernel panic inside gpiochip_remove(). The upstream fix removes the premature cleanup call since no GPIO state exists to tear down.
Critical Impact
A failed pin controller registration path triggers a null pointer dereference in kernel space, producing a kernel panic on affected BCM2835-based systems.
Affected Products
- Linux kernel builds including the pinctrl-bcm2835 driver
- Broadcom BCM2835-based platforms (Raspberry Pi family)
- Downstream distributions shipping unpatched stable kernel branches
Discovery Timeline
- 2026-09-24 - CVE CVE-2026-93274 published to NVD
- 2026-09-24 - Last updated in NVD database
Technical Details for CVE-2026-93274
Vulnerability Analysis
The defect lives in the probe path of the pinctrl-bcm2835 driver. During initialization, the driver prepares a gpio_chip structure and calls devm_pinctrl_register() to register the pin controller. If that call fails, the current error-handling branch calls gpiochip_remove() to roll back GPIO state. However, gpiochip_add_data() has not yet executed in this code path, so no registration has taken place. The gpio_chip.gpiodev pointer remains NULL, and gpiochip_remove() dereferences it unconditionally. The resulting null pointer dereference occurs in kernel context and panics the system. The upstream patch deletes the unnecessary gpiochip_remove() call, relying on the fact that no cleanup is required for an unregistered chip.
Root Cause
The root cause is an ordering error in the driver's error-handling logic [CWE-476]. Cleanup code assumes the GPIO chip is already registered, but the failure path runs before registration completes.
Attack Vector
The condition is reached only when devm_pinctrl_register() fails during module probe. Triggering the panic requires conditions that cause pin controller registration to fail, which typically occur during boot, module loading, or hardware initialization failures on BCM2835 platforms. There is no indication of remote exploitation, and no public proof-of-concept is listed.
// No verified exploit or patch code snippet available.
// See the upstream commits linked in the References section
// for the exact source change in drivers/pinctrl/bcm/pinctrl-bcm2835.c.
Detection Methods for CVE-2026-93274
Indicators of Compromise
- Kernel panic messages referencing gpiochip_remove in the call trace during boot or module load on BCM2835 hardware.
- dmesg entries showing bcm2835_pinctrl_probe failures followed by a NULL pointer dereference at a kernel address.
- Unexpected reboots or boot loops on Raspberry Pi devices after kernel updates or device-tree changes.
Detection Strategies
- Inventory running kernel versions across Linux fleets and compare them against the fixed commits published on git.kernel.org.
- Parse /var/log/kern.log and journald for probe-time pin controller errors on BCM2835 systems.
- Track vendor advisories from distributions that package Raspberry Pi kernels to confirm backport status.
Monitoring Recommendations
- Forward kernel logs from Linux endpoints to a centralized log platform and alert on Unable to handle kernel NULL pointer dereference strings.
- Monitor device availability metrics for repeated unplanned reboots on embedded or IoT fleets using BCM2835.
- Correlate kernel version data with CVE feeds to surface hosts missing the fix.
How to Mitigate CVE-2026-93274
Immediate Actions Required
- Update affected Linux systems to a stable kernel release that includes the upstream fix for pinctrl: bcm2835.
- Validate the kernel package version shipped by your distribution against the commit hashes referenced below before deployment.
- Prioritize patching on Raspberry Pi and other BCM2835 devices used in production or safety-sensitive workloads.
Patch Information
The fix is available in multiple stable branches via the following upstream commits: 3b978fd0a309, 32711f77db06, 68ea6dd23b73, 727f043d699a, b8535f5c77cc, d428863ca8ba, dd6b1919e41d, and f494cfc254cd. Apply the kernel package provided by your distribution once the patch is backported.
Workarounds
- Avoid device-tree or configuration changes that cause devm_pinctrl_register() to fail on BCM2835 platforms until the kernel is updated.
- If a custom kernel is in use, rebuild from a source tree that includes one of the referenced upstream commits.
- Where feasible, restrict unprivileged module loading to prevent probe failures from being triggered on demand.
# Verify the running kernel version and package metadata
uname -r
dpkg -l | grep -E 'linux-image|raspberrypi-kernel'
# After updating, confirm the kernel has been replaced and reboot
sudo apt-get update && sudo apt-get upgrade
sudo reboot
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

