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=1795154326; b=wfIZ1Fa7u8hwIAaCsp2Vnp1Pqczmr29WC4pCeAAHnRtBKIE9vBB1TkLRbyS16uIaPh1T 3wNX12e7AJkpgEdpCPCgU88vUXe4UldEZV+84wmk5jd/jl/uVxvlEHsEEW/q2oB7RyoRT z36Kp8j7u/XZdDvlkRRt2vENiAlgNqNnzrT+HtY701Ir9/spbxdG+HXPeu41SY/C4v3+X j8ZjCKfxcQrqICuSM8CSrM9ZoOJkizsWOXmjgEQng4LPb2qRqbNtM0sW4oubuMB76Q8Uu u4yrqMpejnh31a2PKyXwlLfIJV0sZoS/1dFBVoKOErOqTdmAOtCTFxVwJZLRk62pM/w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154326; 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=SHy2uTDPUXik4CYEPrraeQy6HVhM+zWrQvHxMNPzzW0=; b=BUyrMVDdDAr5n58kLI32/ovFWxQNkoQRteJXy0LjfTK74fS5fGiqjYqhayZ0BRUuFM3H 1fCQq299DNmA0wcazjzzU06yStdj1GRrD6MZtOy1NVSSvCPn1l5wSnfjXwe0OlkAqapJc VtPLPjOYxvzct14UnHuV+pXOguIVtuqcLt2njf0ibfUakRz+/kHKESPkTI2jRbv7QzNdk UkLvyrJ25JxN1OoWrSRb/18wmFO1tQC1WdBgKBPMwhd/rISuMX/wvpVmWqjcpD2PAVMCb XnldEOlROk0oC3dhjTKhbVcF5l4UrNbIHEMGbCCgQP9JJL1Mj9027tBEhoN3eMLyN8Q== 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="G/tpg75M"; 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 19724606A52E for ; Fri, 20 Nov 2026 05:58:46 +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=G/tpg75M Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6960F1F000EC; Fri, 20 Nov 2026 05:58:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154326; bh=SHy2uTDPUXik4CYEPrraeQy6HVhM+zWrQvHxMNPzzW0=; h=From:To:Cc:Subject:Date:Reply-To; b=G/tpg75MCt1C3I+X1rb8T/c1rCQBf7zqX/GQ/CCqw+q9t0T8MiROO85HWhKPkulj9 BcJCNkIi/TzMCiPqV37qjPlO5a9xOc5BuC3nZczr1YonA6a/QaOjfAdannBim6nBlV +Vk4kVYF64db1ry/c0r9Aolyue7D+NiwaixbyFrs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99703: mm/hugetlb: fix mremap deadlock when PMD sharing is possible Date: Fri, 20 Nov 2026 06:51:29 +0100 Message-ID: <2026112003-CVE-2026-99703-241e@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=3056; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=e+gq8mb0CTtZOt1aX4Nbvps9jEWqw9p7hTfrbymDO/o=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/73frHGwuUD+/SGWtftBOjy2LHaJ3nD2gtdL+E/O52 W7/JCc6dsSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBE1HQZFkz18gm2v9aqt9ti yt0vs5mVL/imCzHMT99bx+xzwnit8Ctmi892BizLglYlAQA= 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/hugetlb: fix mremap deadlock when PMD sharing is possible move_hugetlb_page_tables() holds the mapping's i_mmap_rwsem for write while moving hugetlb PTEs. This prevents races with truncation and protects huge_pmd_unshare(), but the move loop must not call helpers that can acquire the same rwsem for read. huge_pte_alloc() can do that when the destination can use PMD sharing: it may call huge_pmd_share(), which takes i_mmap_rwsem for read while searching for a shareable PMD table. Calling it while the move path already holds i_mmap_rwsem for write can deadlock. Avoid that path for PMD-sized hugetlb mappings that can use PMD sharing. Instead of allocating or sharing the destination page table while moving, zap the source range and let the destination fault path populate or share the PMD lazily. Reuse the hugetlb unmap logic for the source-side zap by splitting the core loop out of __unmap_hugepage_range(). The wrapper keeps the existing tlb_start_vma(), tlb_end_vma() and huge_pmd_unshare_flush() behavior, while move_hugetlb_page_tables() can reuse the unmap loop with its existing mmu_gather. The Linux kernel CVE team has assigned CVE-2026-99703 to this issue. Affected and fixed versions =========================== Issue introduced in 5.16 with commit 550a7d60bd5e35a56942dba6d8a26752beb26c9f and fixed in 6.18.64 with commit dd2381dabe0761b6a200a9b4f2eca280e5986faa Issue introduced in 5.16 with commit 550a7d60bd5e35a56942dba6d8a26752beb26c9f and fixed in 7.3.5 with commit 71568db3f9d90c373881c6d438db9afc47a1755b Issue introduced in 5.16 with commit 550a7d60bd5e35a56942dba6d8a26752beb26c9f and fixed in 7.4-rc2 with commit 92daa8652f88c8cfc05f4899a8408a04b02f211e 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-99703 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: mm/hugetlb.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/dd2381dabe0761b6a200a9b4f2eca280e5986faa https://git.kernel.org/stable/c/71568db3f9d90c373881c6d438db9afc47a1755b https://git.kernel.org/stable/c/92daa8652f88c8cfc05f4899a8408a04b02f211e