CVE-2026-93274

A flaw was found in the Linux kernel's Broadcom BCM2835 pin control driver. During device initialization, if pin controller registration fails, the driver attempts to remove an unregistered General Purpose Input/Output (GPIO) chip. This improper error handling leads to a null pointer dereference, causing a Denial of Service (DoS) through a kernel panic.

A flaw was found in the Linux kernel's Broadcom BCM2835 pin control (pinctrl) driver, which Red Hat Product Security has rated as having low impact. If devm_pinctrl_register() fails during device probe, bcm2835_pinctrl_probe() calls gpiochip_remove() even though gpiochip_add_data() has not yet registered the GPIO chip. Because the unregistered GPIO chip has a NULL gpiodev pointer, gpiochip_remove() performs a null pointer dereference that can cause a kernel panic, resulting in a local denial of service. Triggering this flaw requires local access and depends on an uncommon pin controller registration failure during driver initialization, which is why Red Hat rates the impact as LOW even though the CVSS:3.1 base score is 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, moderate).

Red Hat Enterprise Linux 6, 7, 8, and 9 (including kernel-rt) and the OpenShift Container Platform RHEL CoreOS 8 and 9 images are not affected because the vulnerable code is not present. Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2 kernel builds contain the vulnerable code and are affected. For these affected products the fix has been deferred due to the low severity of the flaw and the unlikely conditions required to trigger it; the residual risk is a kernel panic (denial of service) if the driver probe reaches the pin controller registration failure path on BCM2835-based hardware.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.