CVE-2026-99257: Linux kernel · gpio: shared: gracefully handle no-device lookup of shared GPIOs
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to cf73c3fc03c43a8a86fd487c62390b4744eff9ec or 7f9eb6aaf9a3ab7fa2b7dcc38660c27db12d4ec1 when convenient.
Data as of 3 Nov 2026, 11:58 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in cf73c3fc03c43a8a86fd487c62390b4744eff9ec, 7f9eb6aaf9a3ab7fa2b7dcc38660c27db12d4ec1
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade Linux kernel to cf73c3fc03c43a8a86fd487c62390b4744eff9ec or 7f9eb6aaf9a3ab7fa2b7dcc38660c27db12d4ec1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
The vulnerability has been fixed in the Linux kernel. Users should update to the fixed versions identified by the commits cf73c3fc03c43a8a86fd487c62390b4744eff9ec and 7f9eb6aaf9a3ab7fa2b7dcc38660c27db12d4ec1. No additional mitigation steps are necessary.
Description
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.