---
id: "CVE-2026-99162"
kind: "vulnerability"
aliases: ["CVE-2026-99162"]
title: "Linux kernel GPIO shared-proxy use-after-free could corrupt memory"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["embedded", "gpio", "infrastructure", "linux-kernel", "self-hosted"]
not_affected_if: ["default-config"]
published_at: "2026-10-28T11:17:36+00:00"
first_seen_at: "2026-10-28T11:32:36+00:00"
updated_at: "2026-10-28T11:35:45+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99162", "first_seen_at": "2026-10-28T11:32:36+00:00"}]
---

# Linux kernel GPIO shared-proxy use-after-free could corrupt memory

In 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, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- Move to a Linux kernel release that includes the upstream gpio: shared fix (the sources do not name the version).

## Timeline

- 2026-10-28T11:32:36+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99162

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_