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=1795154173; b=RL66ECKgGYnnVj1UedTgEFKqfMdzx4HVZwa4j/LZ0ZTjQUWd5rPtJQo5wFA4y+JqW5GB 07GxxXJXAx841RGy8Rblfx/BM/A68kIeap6ELCqJlbG1u1TwmvjJH9uo3zA8eH/BCbXp6 Szwf14kfblAMLeTlr6VpLF0BVyDNczMGrIaMIPZm2u+f980BpPBAPa5AzGnK0Gp3DcZuA m+7mk/qbY1herD21FFeJmSOAUa0s9Z/uuhllExvIhHS99Y4LYf8TcWDB8NSJQzbkNpT6J asvhoLZc+9MLj9Mm8rxx6FIHdFCxOE+zWC811Xb5C5eT4MXsf2uqEs7q/9wvVvmQMrw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154173; 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=CxWK8tUnrP6XtudY0xdo5SkNGYuens+GVxJoYk4eAog=; b=2pUduZ2mDo7Muc0hUeiyFbswfG/2w2xxmFqSi9WJqRzxK6nYjdniFFSrgeGAO21LvUZ6 q3OmWHIoBeKMeCQ9T5hBYTaUiAOh1mtEpqxtUsL9UVsFw5CN762d/nUs+jGE1M1qxvZsE /70N57WoyUa9FOQX2uQsNTEJYNFWFp11BZ6xJPjFlX1sPG6GP5mexr/IladM3zTx3dP3s tel4UaHUhbEbEbnQz+5f6Jj8M5Fzv+HASo1wD7fQxa1D8gxep3HabPF89S7mGDbbCjtaU H4bxzSjuP4N+6p3D/XWNXGOU1Hj1qQ28NS9HbIap/8E/09I4jgvtgUF3gw+qbeD0urA== 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=oOkKC8WN; 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 9B74D606A320 for ; Fri, 20 Nov 2026 05:56:13 +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=oOkKC8WN Received: by smtp.kernel.org (Postfix) with ESMTPSA id E857A1F000CA; Fri, 20 Nov 2026 05:56:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154173; bh=CxWK8tUnrP6XtudY0xdo5SkNGYuens+GVxJoYk4eAog=; h=From:To:Cc:Subject:Date:Reply-To; b=oOkKC8WNEnZA16g2lxo06Q+TQMzygk/Q+BXMVQg77cImccRoYFMRKIc/ClQk3IOv3 CTxFa4fbLlgw5NWMRLtQ85NiIADe7UNxksuwx8BQpuO7SKcYb2zlMEvpMLy+Ua5gtO QBKFysltBsrorqs3YrbKs1sPJSteKcyQ+Fo7gfyE= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99652: mm: fix deadlock of mremap() against UFFDIO_MOVE Date: Fri, 20 Nov 2026 06:50:38 +0100 Message-ID: <2026112044-CVE-2026-99652-d2d8@gregkh> X-Mailer: git-send-email 2.56.1 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=2797; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=mSPq/8Fdpi2csw9upemvxPEr8xag8uAiQeo1CzddqEc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/71e0/brH6c57qm7WzJnvVuXfvjL9MvcFB1FW8b0uk twVagXPOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAiE48zzI/5byx7fkud288+ r3dl/3Z3aGj3BjEsuBjEE73kirzztMO2R603O16ImuKuBAA= 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: mm: fix deadlock of mremap() against UFFDIO_MOVE With per-VMA locks, UFFDIO_MOVE can run concurrently with mremap() on different VMAs in the same mm. Those VMAs can share page tables, so both operations can acquire the same pair of page-table locks. UFFDIO_MOVE orders the locks by address, while mremap() takes the source lock first. These conflicting orders can deadlock; mremap() holding mmap_lock for writing no longer helps. Move double_pt_lock() and double_pt_unlock() to mm/internal.h and use them for all page-table moves in mremap(). Preserve the source entry checks after acquiring both locks. Remove the comments claiming that exclusive mmap_lock makes lock ordering irrelevant. In move_ptes(), make sure to just recheck source and destination PMD after taking the locks and drop the overly-long comment. Fix generated by an LLM and sent by Chris Mason in private. [ david: use new helpers consistently; simplify description and comments; move_ptes() fixup ] The Linux kernel CVE team has assigned CVE-2026-99652 to this issue. Affected and fixed versions =========================== Issue introduced in 6.9 with commit 867a43a34ff8a38772212045262b2c9b77807ea3 and fixed in 7.3.5 with commit 3627d4eaa7f4426b979d497544ce23cb8884134b Issue introduced in 6.9 with commit 867a43a34ff8a38772212045262b2c9b77807ea3 and fixed in 7.4-rc2 with commit d03df42ddae196f20e9cfb775704e60269eb6b44 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-99652 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: include/linux/userfaultfd_k.h mm/huge_memory.c mm/hugetlb.c mm/internal.h mm/mremap.c mm/userfaultfd.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/3627d4eaa7f4426b979d497544ce23cb8884134b https://git.kernel.org/stable/c/d03df42ddae196f20e9cfb775704e60269eb6b44