From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99190: gpiolib: fix memory leak in gpiod_set_array_value_complex() on error paths
Date: Wed, 28 Oct 2026 11:36:17 +0100 [thread overview]
Message-ID: <2026102811-CVE-2026-99190-818d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2026-99190 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 9b407312755fd5db012413ca005f0f3a661db8dd and fixed in 6.18.59 with commit 78189c0e35abbcdab3b8ab0b764d578c02900734
Issue introduced in 6.15 with commit 9b407312755fd5db012413ca005f0f3a661db8dd and fixed in 7.2.13 with commit 890c3bf08e0fc09eff788a6cfeded7d21b4d3e9d
Issue introduced in 6.15 with commit 9b407312755fd5db012413ca005f0f3a661db8dd and fixed in 7.3 with commit c28846ca1ac6134881114d272314623c8433e372
Issue introduced in 6.12.114 with commit d73d2a569e6212f58d89efc6e66ffbb2386a47b1
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99190
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpio/gpiolib.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/78189c0e35abbcdab3b8ab0b764d578c02900734
https://git.kernel.org/stable/c/890c3bf08e0fc09eff788a6cfeded7d21b4d3e9d
https://git.kernel.org/stable/c/c28846ca1ac6134881114d272314623c8433e372
reply other threads:[~2026-10-28 11:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026102811-CVE-2026-99190-818d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.