Live › vulnerability › CVE-2026-99162
Go to dashboardIn the Linux kernel's GPIO shared-proxy code, a lookup table could keep a pointer to a kobject name string after that string was freed. The fix duplicates the string so the pointer stays valid, which prevents a use-after-free.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
Systems running a Linux kernel without the upstream gpio: shared fix that use shared GPIO proxies. The sources do not say which kernel versions or configurations are affected, so a team should check its kernel build against the upstream commit.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99162")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.