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 EF5351A680B for ; Fri, 19 Jun 2026 14:00:45 +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=1781877647; cv=none; b=pVN0xI6BriGiImRHhtVBoD+2dUqudDVeMn2363Gn7HS6xd4yPPxUOhO4e9Nmumbu2N60b7auM4uBmZTUgMz7PTSmlsWBSWF4igQmp/sWZz6yInKMznthnlaVUnua4D583NgsgIIt8hA4dEcN1wjxXp1GkUKqZ0YojymFN2fKhbc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781877647; c=relaxed/simple; bh=JCly+1I9EHkYJtF6mnIfArlK6MxqDz34tHBVjWuXb6w=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=W+tIqFj2/8XNKjicNH+CEVUShOWGMKXXNHTSdpEsTF2gnuZxPjSz9zgPrsqV6VXrpZyXeBLfmMz+qSzjerHNkyzt/l2W2WK10dpZTgI5CloU/6p2HZON7441AxEt+jQbb6nh+Qp+/CKAzp5gj3d67tTEWExymp6mtbdLNFdRst0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=J9Dm21iY; 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="J9Dm21iY" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 006BB1F000E9; Fri, 19 Jun 2026 14:00:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1781877645; bh=KwFuxV1gFLOfw315pu0NFtPSxsVj1aaqfYjuhza8Yoc=; h=From:To:Cc:Subject:Date:Reply-To; b=J9Dm21iYk5DucllOsWgdailxHa6MqFt0eGM2pohtC2gknHosREWZAQTBm6m2jhchh XlxJOmM8NjnhasW2mf/KDMxY6GdPJOhyyhwzplWv/aRcKdy/D2vIW35H0Zsx3yIsUR YnGe+jJTN3QIl9IjMcR7lZmHGZ1pN78DPQJGqtKc= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-52908: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible Date: Fri, 19 Jun 2026 15:59:36 +0200 Message-ID: <2026061935-CVE-2026-52908-ecea@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=3195; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=2cAVNX12SCnWU6240Ran4WIp31EIih0PdOe1XsVVCqI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmm3u7vuW4fqakwmL/1hf1diTMm7Gnv9dX03j7rnnGba Udx1XyPjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIXi/Dggv9XowXXV/m11jG fzibfefBO0vRSoYFE2Z07DNMWxJlJ8jfktx+btXzFftbAA== 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: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible If IB_MR_REREG_ACCESS changes from RO to RW then the umem has to be re-evaluated to ensure it is properly pinned as RW. Since the umem is hidden inside each driver's mr struct add a ib_umem_check_rereg() function that each driver has to call before processing IB_MR_REREG_ACCESS. mlx4 has to retain its duplicate ib_access_writable check because it implements IB_MR_REREG_ACCESS | IB_MR_REREG_TRANS by changing both items in place sequentially while the MR is live, so it will continue to not support this combination. The Linux kernel CVE team has assigned CVE-2026-52908 to this issue. Affected and fixed versions =========================== Issue introduced in 6.2 with commit b40656aa7d559adc1fe689396dc58b92a9a27286 and fixed in 6.6.143 with commit 09dc18894148381d3bfc550083b1236043870dce Issue introduced in 6.2 with commit b40656aa7d559adc1fe689396dc58b92a9a27286 and fixed in 6.12.94 with commit eba5df21eda0fe7418efbea2f799f8ea1b8ca94c Issue introduced in 6.2 with commit b40656aa7d559adc1fe689396dc58b92a9a27286 and fixed in 6.18.36 with commit 2904e985a2917b5dac65df82733065e78a65fc9d Issue introduced in 6.2 with commit b40656aa7d559adc1fe689396dc58b92a9a27286 and fixed in 7.0.13 with commit 50334a05a950840b39a1ce3d2a173b4183db9b3e Issue introduced in 6.2 with commit b40656aa7d559adc1fe689396dc58b92a9a27286 and fixed in 7.1 with commit badad6fad60def1b9805559dd81dbab3d97b82aa 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-52908 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/infiniband/core/umem.c drivers/infiniband/hw/hns/hns_roce_mr.c drivers/infiniband/hw/irdma/verbs.c drivers/infiniband/hw/mlx4/mr.c drivers/infiniband/hw/mlx5/mr.c drivers/infiniband/sw/rxe/rxe_verbs.c include/rdma/ib_umem.h 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/09dc18894148381d3bfc550083b1236043870dce https://git.kernel.org/stable/c/eba5df21eda0fe7418efbea2f799f8ea1b8ca94c https://git.kernel.org/stable/c/2904e985a2917b5dac65df82733065e78a65fc9d https://git.kernel.org/stable/c/50334a05a950840b39a1ce3d2a173b4183db9b3e https://git.kernel.org/stable/c/badad6fad60def1b9805559dd81dbab3d97b82aa