Skip to content
statance
MenuClose
unknown

CVE-2026-99257

gpio: shared: gracefully handle no-device lookup of shared GPIOs

Published 3 Nov 2026 · Source updated 3 Nov 2026 · Retrieved 2026-11-04 15:02 UTC · This record may be stale; verify the source

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

In the Linux kernel, the following vulnerability has been resolved:

gpio: shared: gracefully handle no-device lookup of shared GPIOs

We use platform lookup tables for shared GPIOs. This mechanism needs a struct device to work so fwnode-based lookup with no device associated currently causes a NULL-pointer deference.

Adding this functionality will require a larger rework and it has never worked anyway so add a check that allows the kernel to gracefully handle this situation with an error ahead of implementing that functionality as a new feature.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: a060b8c511abb0997381b397e52149a5e3e5259a to < 7f9eb6aaf9a3ab7fa2b7dcc38660c27db12d4ec1; affected: a060b8c511abb0997381b397e52149a5e3e5259a to < cf73c3fc03c43a8a86fd487c62390b4744eff9ecSee vendor advisory
LinuxLinuxaffected: 6.19; unaffected: 0 to < 6.19; unaffected: 7.2.13 to ≤ 7.2.*; unaffected: 7.3 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed