Quick answers
- Is CVE-2026-93274 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93274 being exploited in the wild.
- How severe is CVE-2026-93274?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Linux multiple versions affected (see kernel git history).
- Is there a fix for CVE-2026-93274?
- A patch was published on 2026-06-30. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93274 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-93274?
- Check whether you run Linux at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The bcm2835_pinctrl_probe() function calls gpiochip_remove() in its error path even when gpiochip_add_data() has not yet been called, causing gpiochip_remove() to dereference a NULL gpio_chip.gpiodev pointer. The vulnerability is a logic error in the cleanup sequence that triggers only when devm_pinctrl_register() fails. A fix removes the unnecessary gpiochip_remove() call since no GPIO cleanup is required for an unregistered chip.
Affected products
- Linux Linux multiple versions affected (see kernel git history)
Timeline
- 2026-09-24: disclosed
- 2026-06-30: patched