VulnerabilityPublished 28 Oct 2026

CVE-2026-99162: Linux kernel · gpio: shared: fix use-after-free bug when adding shared proxies

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to bd22f7e63509fa758cf500d9af3e88a3d3df96be or 8861491f8501516429e0e6c9d7a056480047227c when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in bd22f7e63509fa758cf500d9af3e88a3d3df96be, 8861491f8501516429e0e6c9d7a056480047227c

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to bd22f7e63509fa758cf500d9af3e88a3d3df96be or 8861491f8501516429e0e6c9d7a056480047227c.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ a060b8c511abb0997381b397e52149a5e3e5259a, < bd22f7e63509fa758cf500d9af3e88a3d3df96be	Fixed in bd22f7e63509fa758cf500d9af3e88a3d3df96be
LinuxLinux	Affected ≥ a060b8c511abb0997381b397e52149a5e3e5259a, < 8861491f8501516429e0e6c9d7a056480047227c	Fixed in 8861491f8501516429e0e6c9d7a056480047227c
LinuxLinux	Affected =6.19	Fixed in–
Red Hatredhat/kernel`pkg:rpm/redhat/kernel`Other threats	Affected =6.19	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

In the Linux kernel, the following vulnerability has been resolved: gpio: shared: fix use-after-free bug when adding shared proxies The GPIO lookup table can stay alive for longer than the kobject whose name string's address we're assigning to lookup->dev_id. Fix a potential UAF by duplicating the string.

References

Community reviews

Loading reviews…