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=1792759241; b=BnDBDLWQlD3YeCVF8WKnf/o+U3WfhKKurzOar/fVAggcWZx6aPjdNODe9T1OyUCuzl9p 9v0epw7mSXx30Hx7wMrGQxnHXa+ARLtUW0m6nTHFE21gTLOIadF8QIDrWcKp/VPowydqX pFj0F9lMaQmIDI9zojPkQFis8mAu0Em2D7l2oI6FbK5FYgCvnoSX7vIA7OSHMcvpoItrg epVeiXqW2Cq2xLovash0Y+Q5SppPx6LHfzYW567pGu0xgXBOPKrbjGH3ksfe5n4EsuAQx uhOraKd1T52T10fImCDuH/R+oSm4oWnL5uHjznvGqSNMDepsLSdWIuVD3MxU7ShN9Ag== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792759241; 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=dPt0NjuZ6XV8rIQKoE6RoE2COzz3d9UAatbMr0nfNCY=; b=tWJ/tm/y4ZETZxqSdSZyQKwQaQ0J0jdM/iljEOzn4VTW2h6nxfRSV6gteQcwR7Q8qB0l 0JVV83pziFwR34+4EGrOxKr93U5o0fY+22vMz/rILqd2NhYJtlXiqQkDIJ9nOvVuEpRD4 5a8YQHd0KFZ3DUtaH5XOs82Uda2GC488ZZaWqoPy5rwtjOJ2I7OtKOtv9Ig3aHz7EuGy+ 8N7hgBzWzy6dAkHQN8g5q6XXYwjLn5yUOJHD/Ox83xC0bMSn+nUoqwDejlBZ52D4PVNGT bod2UdSTS9ycvaRIa1yoCXUJk8lp8pxvqx2j8DdcHL83ltxHY/I0u8t16HztL+HYyOA== 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=grQ0KHdk; 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 1579A606A31A for ; Fri, 23 Oct 2026 12:40:41 +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=grQ0KHdk Received: by smtp.kernel.org (Postfix) with ESMTPSA id 37A9C1F01825; Fri, 23 Oct 2026 12:40:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792759240; bh=dPt0NjuZ6XV8rIQKoE6RoE2COzz3d9UAatbMr0nfNCY=; h=From:To:Cc:Subject:Date:Reply-To; b=grQ0KHdkukJN26fGyoBa8N7M+nMGVqsisLnhHTmtV4ki0bJOFvjTQbo34z0qxpA3u vlfDdcynR9ftQnOvS7T2a5V70Wx9JPWI6aNclxkfBXqgvgcVYs/OjZ6J9Pfa9yrD7r MTirULM6Z0yZpUFkv+IeyMnmD9EKZXNLuqt4RH48= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99050: gpio: mpsse: fix race when arming the IRQ poll worker Date: Fri, 23 Oct 2026 14:20:52 +0200 Message-ID: <2026102329-CVE-2026-99050-c8be@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=3161; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=IlThvtWVp5HjIOrcWbb0SRppKkk5vsc1gqsqYGt+o2c=; b=owGbwMvMwCRo6H6F97bub03G02pJDFm3Ay6a9V36+2OzyIXXufHKH4OuKrxh7JXezPUkovGtf Gozc6RNRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAExkngnDgpatvyYzciz+vLOh srRVbMXZZXrrPRjmmVd6T9/27+wO29IjhZyqBevVPiteAAA= 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: gpio: mpsse: fix race when arming the IRQ poll worker gpio_mpsse_irq_enable() arms the poll worker before publishing it: schedule_work() runs before the worker is added to priv->workers. If gpio_mpsse_disconnect() walks the list in that window it misses the worker, and once disconnect returns, the USB core frees mpsse_priv while the orphaned gpio_mpsse_poll() work keeps accessing it, causing a use-after-free. Fix this by publishing and arming the worker in one irq_spin critical section. Teardown walks the same list under irq_spin, so a worker found on the list is guaranteed to be armed, and cancel_work_sync() handles it whether it is queued or running. A worker armed after the disconnect walk would still be missed, so also set a new priv->dying flag under irq_spin before the teardown walk, and check it in the same critical section, freeing it via kfree_rcu() instead when the device is going away, since kfree() would be called with the IRQ core's raw spinlock held and may sleep on PREEMPT_RT. schedule_work() is safe to call with irq_spin held, and the next probe gets a fresh mpsse_priv, so the flag never needs to be cleared. This issue was found by an in-house static analysis tool. The Linux kernel CVE team has assigned CVE-2026-99050 to this issue. Affected and fixed versions =========================== Issue introduced in 6.18.6 with commit 472d900c8bcac301ae0e40fdca7db799bd989ff5 and fixed in 6.18.57 with commit 76390ac0bca7e5058b7482eb4d951c3bda5df812 Issue introduced in 6.19 with commit 179ef1127d7a4f09f0e741fa9f30b8a8e7886271 and fixed in 7.2.11 with commit c0071ee496e1228976c72b096f529503222708a0 Issue introduced in 6.19 with commit 179ef1127d7a4f09f0e741fa9f30b8a8e7886271 and fixed in 7.3 with commit 7efa1a1953cd6b20b23a3524d5b4b81789c6ef25 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-99050 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/gpio-mpsse.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/76390ac0bca7e5058b7482eb4d951c3bda5df812 https://git.kernel.org/stable/c/c0071ee496e1228976c72b096f529503222708a0 https://git.kernel.org/stable/c/7efa1a1953cd6b20b23a3524d5b4b81789c6ef25