Menu

Star on GitHub · 3.5k

CVE-2026-93274

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()…

Published Sep 24, 2026EPSS 0.20%

Overview

CVE-2026-93274 is a known-severity vulnerability. It was published on September 24, 2026.

Technical description

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-93274?

CVE-2026-93274 is a known-severity vulnerability. It was published on September 24, 2026.

How severe is CVE-2026-93274?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-93274?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-93274?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-93274 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

CyberStrike v2 is here — more intelligence, greater reach