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=1795098872; b=16K0Lb/dz04Xmy0zBnykkVoW+dEDqnbeIxDZH8HZLlHTFpREwqzKCjA/rAGVIPxagPTx oxPbkCTEEn0r6lV4BxQzKZrbTWiP7ZWeAl8JmTUovn7SGqo+WE3PwFrewqnxN7wIHl42K Tck8fxQguZyeNwmqiC0yKYiObBSRfbXu10ZIsUvbZaVUaKK8dK35DZIH1Onopf7q+fhiS 9Rhc1GxZH6aQj0Uv7cQkBU26LroswwsFMY1BSZLrOeuSJwymImsF1ygXKEWa5kS53XRN7 NktKd5HBlYK6ZESh5J1aMVi9ID0ddF/IKi2NFvFDFdQCih3wJ0QAbiQlMmrCnw4KwMg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795098872; 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=B6DIhLjA+s2u4qqUeXBcBuZSm3fpqzd6f+qk9Jhtmp4=; b=v/Nd6gvL23zuI2eHoPN5nIJVqtx3IjjMJ3vtJorTkNkZayDu42NE7vbwkg7NXi3Xs3ym hSJsQvJ5z2DNVTGqaURFIAIYHg1fhXsK/oLzq2tjUqAb0D8u5y7W/fQ+kBxJAXDaWO1Qq COi/d7SMNj6OgwVmIYF3TdD/p9nVGwZCFqDYWz2q4bDYW9j0BoUyDIfasfAuXAi0Z1UnA qg3Y5kTXqWhNtk4T3Y5SdMy+1KaLAtV6jB1wrJDlvOwTcJFSkT9rZHXdqMAtf4e+ozgy1 r9YRsmsrKsx0Reg8xftm9LBnD+JzJJSrqTZo9w8VxqyDyhyii2KnUNS+afdCeQabkDw== 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=zuWlshsH; 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 277CF606A320 for ; Thu, 19 Nov 2026 14:34:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=zuWlshsH Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5B2801F000C4; Thu, 19 Nov 2026 14:34:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795098871; bh=B6DIhLjA+s2u4qqUeXBcBuZSm3fpqzd6f+qk9Jhtmp4=; h=From:To:Cc:Subject:Date:Reply-To; b=zuWlshsHkZQSiS22+iTg4CxlUMaPkFOdFnPWDYOhDjBHbRCxEq98kDG+rYEkcN5EF ofjja9a4aB/b8i3EZ8zsbM4gRPv2ZXdCAh9fp2SQY9+fC2j7K5QSXoFZ6+xUzxcRmL aHYkiurinu7m+Ji45rGDi5M6q+4nCpvnh++t3F48= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99350: rxrpc: Fix update of call->tx_pending without holding lock Date: Thu, 19 Nov 2026 15:24:08 +0100 Message-ID: <2026111947-CVE-2026-99350-a67e@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=3678; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=e1i6H9E475YtN37XMsVfdMITzIrT7u/GVVmBl+2+Sus=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2Uo6/5i1Jv7YznN50/lPPwK/6jRuaki0fvn0mtQmo /3J6+0vdsSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBE0h4yLFglo2Cst7wr//vc VQtn3gy5N/VD1BWGBZuv7ata/f9B5SOB5B0r7R/ulhc7dhAA 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: rxrpc: Fix update of call->tx_pending without holding lock Currently, rxrpc_send_data() updates call->tx_pending just before it returns - but it won't be holding the call->user_mutex when it does this if a wait was interrupted by a signal. This would allow a parallel sendmsg() to race. Further, both the callers of rxrpc_send_data() call it with the lock held, and then it returns an indication through the parameter list to say whether it has dropped the lock or not - after which the callers both just drop the lock if it's still held. Fix this by: (1) Moving the release of call->user_mutex down into rxrpc_send_data() and get rid of the indicator parameter. This makes it easier to see where the lock is held. (2) After waiting, if the attempt to reacquire the mutex is interrupted, just return directly there rather than going to out_unlock (3) Restricting the txb variable to inside the buffering loop and leaving ->tx_pending set until we've queued the buffer. Note that there's a slight change in behaviour in that wait_for_space failure now doesn't check for completion because it doesn't hold the call user_mutex. The caller, however, should re-issue the send and pick up any error at a second attempt. The Linux kernel CVE team has assigned CVE-2026-99350 to this issue. Affected and fixed versions =========================== Issue introduced in 6.0 with commit b0f571ecd7943423c25947439045f0d352ca3dbf and fixed in 6.12.118 with commit 35f7a69391ca0819d04ca6db3c2355848d633e16 Issue introduced in 6.0 with commit b0f571ecd7943423c25947439045f0d352ca3dbf and fixed in 6.18.61 with commit 965456110cf6952cc4eec80761171503e6e424df Issue introduced in 6.0 with commit b0f571ecd7943423c25947439045f0d352ca3dbf and fixed in 7.3.2 with commit ec98e8bdbde85e2dd2d43570e25b52bdfac1735b Issue introduced in 6.0 with commit b0f571ecd7943423c25947439045f0d352ca3dbf and fixed in 7.4-rc1 with commit 7801c42c3bb737cfb06194a383873fcad8daacf5 Issue introduced in 5.10.140 with commit 79e2ca7aa96e80961828ab6312264633b66183cc Issue introduced in 5.15.64 with commit 2bc769b8edb158be7379d15f36e23d66cf850053 Issue introduced in 5.19.6 with commit 091dc91e119fdd61432347231724f4e861c6b465 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-99350 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: net/rxrpc/sendmsg.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/35f7a69391ca0819d04ca6db3c2355848d633e16 https://git.kernel.org/stable/c/965456110cf6952cc4eec80761171503e6e424df https://git.kernel.org/stable/c/ec98e8bdbde85e2dd2d43570e25b52bdfac1735b https://git.kernel.org/stable/c/7801c42c3bb737cfb06194a383873fcad8daacf5