From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 307E7379EDF for ; Thu, 21 May 2026 12:18:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779365889; cv=none; b=Cu294TJwlOERB5jlzXvHwupiJhXRVZ/dHgMa20BcMN0T8hBDknZoithxQOWhgzVs6nL7nhuYgauluDyWQj+xsWWiO5gT6kVfpGS6PmK6kyHGpYNbpaDc/nVudG9OQ4RVk0rTprPGlWDlOeFbAm0gHQckid1p9F9bAVIZPP9fzg4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779365889; c=relaxed/simple; bh=2XX5xj1DgOhhz8Y+FSFmKUX1DAkWzebw5SJC4NsxLG0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=cUsrT/0eDMe2bAQZLwkZVlTy/VuGHZGqg699G/Z2CpL/ZSKk8aakOa8tNzm+YEf1YoXYNS53JuheYuzEDXKmgNBTE/iU6Pn6n7OAh39V+0LMsei9xppmEZIpRcVOcUsWcGbBX/jJ8u+VtoxzOHrLumpDWUFSJvslFI9BOrLGN/Y= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=poTv02dK; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="poTv02dK" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 51F811F000E9; Thu, 21 May 2026 12:18:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1779365887; bh=qEKQm/XK0WRbsKZNcMIhxlEhtMNk3gJxilbNBN2T2VY=; h=From:To:Cc:Subject:Date:Reply-To; b=poTv02dKhrJOQjK+t0xb72H5sI7BoQ+df7CRUELir0v0tGB3yBquVPJW8RaOdnQqu CoNkXC/1VBV4j5xM25WdfSG2U/0RwRRcsnPM0j1bv/aAzwmE8VUkIXa+H23q6ReleH SVPZmbntDuFy302/J5yE8QgqfTZxsTjVJmxO88DI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43502: net/rds: handle zerocopy send cleanup before the message is queued Date: Thu, 21 May 2026 14:18:02 +0200 Message-ID: <2026052159-CVE-2026-43502-01ec@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3311; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=+NHvjDMhkBNUR6BU2k61+A2Tbb2CjOZyVntIN20pYSQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFl837+vFvViyZs9eWui2EXFzqVKjwWzvyY1T+97sNr9Y XDG8qDSjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZiI5X+GObzfL5QZvNM47XBy g53U9vsHzhQW+THMMz5l+XSzwzt75R4/lVONcTdYlyYXAwA= 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: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path. The Linux kernel CVE team has assigned CVE-2026-43502 to this issue. Affected and fixed versions =========================== Issue introduced in 4.17 with commit 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 and fixed in 6.6.140 with commit 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e Issue introduced in 4.17 with commit 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 and fixed in 6.12.88 with commit 3abc8983b2bae3f487f77d9da5527d7d6b210d46 Issue introduced in 4.17 with commit 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 and fixed in 6.18.30 with commit 14ef6fd18db2494098b21e0471bf27a1d8e9993e Issue introduced in 4.17 with commit 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 and fixed in 7.0.7 with commit 0f5c185fc79a59ee9991234dd6d2a3e5afa6e75b Issue introduced in 4.17 with commit 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 and fixed in 7.1-rc3 with commit 44b550d88b267320459d518c0743a241ab2108fa 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-43502 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/rds/message.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/21d70744e6d3bbf9293aa1ee6fba7c53ad75275e https://git.kernel.org/stable/c/3abc8983b2bae3f487f77d9da5527d7d6b210d46 https://git.kernel.org/stable/c/14ef6fd18db2494098b21e0471bf27a1d8e9993e https://git.kernel.org/stable/c/0f5c185fc79a59ee9991234dd6d2a3e5afa6e75b https://git.kernel.org/stable/c/44b550d88b267320459d518c0743a241ab2108fa