From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793187677; b=epGHYzjWx/cLvZCi82BVd95gx0fNk/E2qyjHYxF0g9APY7mHV95G64BueHdNaFD9oxWt I6Sc/Rrz6dCSiid82jP9M8aH2bhj3r7Yr9TlZcfkBBkR/JrzhZziZVsLzpE7mYRtxJ6Nq 8X07cPHMs1Rq5ymHHpyCamUOsOlZVTvAq2ONfvG/AY0otcLs1GNMVAif3zSemza+qiCFf c/HpuMqwQWWazxUPmftvEleU8sjGjW+h5C4vwNGSv66tcmPDx6+e8Fvab+scZNIk/xnNS MakRL3xcuxfY27JAv/1ioUGCrVtkDUakgWU/COdLp7i5f/xV6o1usI0OD9JtkaU4i6Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793187677; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=tAak7cs87+WFqFJW0Ensb4SQjsdvrdYN+L2TtzmtTAc=; b=UWy3uFW9t7tXD2QFbt9ZpOMHo2hUoYPjsNKHCJoKCljsREHxMqOIk1bb9TerW5SK7UWk my0PdMFjs0Xiqh8VYU46gbrSG/JaCQjslpbLalKZckv6+gpqzWnoLMnwtT1fCxhaeSrYC VDMGZ5AOu2f7B+3FaW2ueHhoHABFqNJQLJaZDHoiRWt4PFc5W7B5Dk/QgGdHr7KGiU0D9 0389yHREAm6/QfHelaMphHwW2tBnFpTllNEpGvIjUmVwiWvx53iiq9gCW8OqRwRzieDOC 5N9U8SdRwYX3loJMGkP9L+5ejXOIJbtIVQUq2KmJfBtrqk48jnDRE9SZk+0vQWSrGkg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=pa5UpZ8u; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AA508606A31A for ; Wed, 28 Oct 2026 11:41:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=pa5UpZ8u Received: by smtp.kernel.org (Postfix) with ESMTPSA id A67F51F01828; Wed, 28 Oct 2026 11:41:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1793187676; bh=tAak7cs87+WFqFJW0Ensb4SQjsdvrdYN+L2TtzmtTAc=; h=From:To:Cc:Subject:Date:Reply-To; b=pa5UpZ8uWp0aKrJup8VYnNewYoOQHA0Ww5gDvZUfhl2Y9KPwKX8ZvAWfsH3fxm1+f 7QzKUBKDcqpCtg3aUmROaNP6NZkVMe++4z2RXtKFrAZYTHIcrx7tizwppWMDIMKwQI zXszuTQ0gwe+5gHexJ8kuWwybGMkU4GjTnOk7eRw= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman 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 Message-ID: <2026102811-CVE-2026-99190-818d@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2421; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=TvIyJqydndX8beZf0VTgZeJ4GZq0j2J+e1qAw6Y18x4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkPz99vrsxlmWTuX2HCEL3MTCZ8upRLk/DxLdmGx4yY9 8x5aD6rI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACZStJZhfty3js2X2zMvHvwx /6rYi0IFoUNh1gwLOqZIf/tm9VxHmUHt7Ma+gNd80+ZdBAA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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