---
id: "CVE-2026-99190"
kind: "vulnerability"
aliases: ["CVE-2026-99190"]
title: "Linux kernel GPIO: memory leak on error path in array value setting"
severity: "low"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["embedded", "gpio", "infrastructure", "linux-kernel"]
not_affected_if: ["default-config"]
published_at: "2026-10-28T11:17:39+00:00"
first_seen_at: "2026-10-28T11:32:37+00:00"
updated_at: "2026-10-28T11:34:13+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99190", "first_seen_at": "2026-10-28T11:32:37+00:00"}]
---

# Linux kernel GPIO: memory leak on error path in array value setting

In the Linux kernel's GPIO library, a failed gpiochip_set_multiple() call makes gpiod_set_array_value_complex() return early and skip freeing temporary bitmaps. The result is a kernel memory leak on an uncommon error path, with no direct code execution described.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

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

## From the sources

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

gpiolib: fix memory leak in gpiod_set_array_value_complex() on error paths

A drive-by review by Sashiko reports that, after a failed call to
gpiochip_set_multiple(), gpiod_set_array_value() returns abruptly,
bypassing the freeing of possibly alloced bitmaps, potentially leaking
memory. It is an unlikely error path, but is possible.

Defer the return code check until after the bitmap_free() block.

---

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