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 1F88D4EE868 for ; Fri, 4 Sep 2026 16:50: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=1788540609; cv=none; b=E2TwXx9Gg83FQ3CjkYzU2fbPqs/OiYoU67RkWIuTkjJZbKPV7yrSW/gWXb0d26fe0hCHF178r+jvnZZ4650DERextFCzn1Rvmlvvi7V8LI0yoQVxVzrwGR68CCSmJqTI3wUADl6sJQoA3eZ1W9WfX6REzza0043+9ADt9qlOmzk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788540609; c=relaxed/simple; bh=7QLWtywK9D882+WIKJqFH73iMUF0LdesTQN44PtHUnY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=TLdCKkgH7BmOX082VKTR9d0EhikFPKIew5lL/RNJN6D2d4d/x9oo+hMm40dmWSYbMuu6vfGKFCukSnBZhKv/t6+Bje9BxlrX1vuTTCaztf5A2vAcHMkCi0fSrDAz/UCRrjGEu3C91vTY9uXRN6Ulxu7K+utLrR5DaxjOnH3CleE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=fxMC5c2Z; 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="fxMC5c2Z" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 95C971F00A3D; Fri, 4 Sep 2026 16:50:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788540607; bh=5x8a9v+jE0ksdoTglNbJCl1Z+Cf3wqnlUNrgDfFSCdY=; h=From:To:Cc:Subject:Date:Reply-To; b=fxMC5c2Z6i8GmeqYBpTP9FUSrs7495s4qQZve9+GL7mqyqst8ZdNBlVQrtFZ27M0t kg1WSa17rybGqBk+SMvf7B4FG9XqVmWAgLyrZtkLxMGTjDWA8vRkWX7YY+jIEUG8tC kA0hoFUo21zHyy8Hvlg7PaOjhRCy2NnN53cNlVUs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80880: IB/mlx5: Properly support implicit ODP rereg_mr Date: Fri, 4 Sep 2026 18:46:47 +0200 Message-ID: <2026090436-CVE-2026-80880-0161@gregkh> X-Mailer: git-send-email 2.55.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=3384; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=6Kd+/s0ASA/kfLMUPIiaW9hej5RmQ0k/iGT5D08Li4s=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmzvr652Stev2H93wleE9i8L7yrsBbIszpcPf3czOy+c pdnX7Oed8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEwtYxzJVaet6pQm9fgJPQ tEO9Sq+Xf21h38sw31UwusXqw2HGw3dWm+Tby7NPTT4dDgA= 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: IB/mlx5: Properly support implicit ODP rereg_mr Due to all the child mkeys in the implicit ODP configuration we cannot change anything in place for the parent mkey. Instead the whole thing needs to be rebuilt if any change is requested. If the user does not specify a translation then force the implicit values which will then fall through the logic into mlx5_ib_reg_user_mr() to allocate a completely new MR. Since implicit children were also touching the mr->pd, this removes another case where the access was racy. The Linux kernel CVE team has assigned CVE-2026-80880 to this issue. Affected and fixed versions =========================== Issue introduced in 5.11 with commit ef3642c4f54d3493c92c71faf46139b2473bc532 and fixed in 5.15.212 with commit cbc9982c8573fb9e35040063aa78c8ebe768a1ff Issue introduced in 5.11 with commit ef3642c4f54d3493c92c71faf46139b2473bc532 and fixed in 6.1.178 with commit ee914ef54a7e707453ecb43eb30fb0a5c6dd0d69 Issue introduced in 5.11 with commit ef3642c4f54d3493c92c71faf46139b2473bc532 and fixed in 6.6.145 with commit 94f7e50eb6b2ce7fbd9aeac1db22460d2013a3fb Issue introduced in 5.11 with commit ef3642c4f54d3493c92c71faf46139b2473bc532 and fixed in 6.12.97 with commit eb7cb798e563b3f3b3baeb9cc6f7455764267e50 Issue introduced in 5.11 with commit ef3642c4f54d3493c92c71faf46139b2473bc532 and fixed in 6.18.40 with commit d4f84bfa089fe71f775d25beb29303e844494c25 Issue introduced in 5.11 with commit ef3642c4f54d3493c92c71faf46139b2473bc532 and fixed in 7.1.5 with commit 5d02b9a2efd11d28d2a8feac7769686b1b871d9c Issue introduced in 5.11 with commit ef3642c4f54d3493c92c71faf46139b2473bc532 and fixed in 7.2 with commit ee7a8335069150c3f1893a697ab30bbeca00d796 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-80880 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/hw/mlx5/mr.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/cbc9982c8573fb9e35040063aa78c8ebe768a1ff https://git.kernel.org/stable/c/ee914ef54a7e707453ecb43eb30fb0a5c6dd0d69 https://git.kernel.org/stable/c/94f7e50eb6b2ce7fbd9aeac1db22460d2013a3fb https://git.kernel.org/stable/c/eb7cb798e563b3f3b3baeb9cc6f7455764267e50 https://git.kernel.org/stable/c/d4f84bfa089fe71f775d25beb29303e844494c25 https://git.kernel.org/stable/c/5d02b9a2efd11d28d2a8feac7769686b1b871d9c https://git.kernel.org/stable/c/ee7a8335069150c3f1893a697ab30bbeca00d796