Live › vulnerability › CVE-2026-99190
Go to dashboardIn 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 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 Linux kernels that include the gpiolib change that adds the early return; the sources do not name affected versions. The bug only fires when gpiochip_set_multiple() fails, which the source calls unlikely, so it mainly matters to hosts that drive many GPIO lines through the array API. Hosts without GPIO hardware or with a kernel that has the fix can skip it.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
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:
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99190")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.