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=1795154317; b=NH50vgtM6hdGulAMkbMzQEsf1L3QoLU4mYOxA6tsc0xei9qi3Q7MKf1M0uHiiomcHzKo H2un4FQP49OpeafQHog61GJZFu5wuHJQFbJvb27hxLifeDN4o1cJ/gQmbRG2545QXwa52 /VvfNnLsp3pBLbc4IwzfzFu9/Nyd5ELeizl1J0lrbV/xG1ifeiP3qYkvBwHOxIu/+fwwA 6vvflz/KCH6zHOurWeY2jzNiQNDdNDpp71OrBvvAchtN9cbBN+zPZZnWvMC4LeQWewxMN I4D1OmWPtEnp8NCvacp12aLVxrAAtzoJIdOknGMerZdm6MOWFHeCo9z9ma/TLYbsiPg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154317; 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=ZJoDcw3RiArF/QqlVbVLWK7hdwvpCu3KgzeeG3B/GuM=; b=buAqkHxtezJc+cRzMMkKvewyi9dw4J6yl4IxTimu5fc3RHkHVnM0kqjrZ+6oqpYDQknk CiBBRo5mC4XMrPSvaLWEWm4hAxmuuQkSeAwLZpUoq36DUpbV76vVm7sz408RR66DxCnFe HxhwyMewMMZUVBxNQPTjRh/z6i67penGpwu9gRxVqsoYEe9GVjqufalAnBh/GjxbC3ofq u2eGmnqqCaEEJDe2uw9CavluUbjUOzQ50lqMsWL0jbJzimu08RuZpZlUrPWT/yZrwS9/p Kl7S7uTbnUcTpskFgpBWu+gH4BbPXML5wyiKZoqgrnoStxdjFntVP39SZP3HSnP5kYw== 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=FG04KzlX; 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 782D560A383F for ; Fri, 20 Nov 2026 05:58:37 +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=FG04KzlX Received: by smtp.kernel.org (Postfix) with ESMTPSA id C7B591F000CF; Fri, 20 Nov 2026 05:58:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154317; bh=ZJoDcw3RiArF/QqlVbVLWK7hdwvpCu3KgzeeG3B/GuM=; h=From:To:Cc:Subject:Date:Reply-To; b=FG04KzlXpi1E+9zc4v+4140yKzahR4Syu0Pl0D08STeawEpyAhyf3VidW2N5q281N cl/Icqy6HUeuXgzHrTG5hYJ3dCyEL2FipEqRk4cwULozJeu96RjQqj4hjpafvL9PEW 0uMifzqLuEfg1GTP3FvdQURIAsLyY1Tre6TBO7gk= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99701: mm/ksm: fix userfaultfd protection during merge and unmerge Date: Fri, 20 Nov 2026 06:51:27 +0100 Message-ID: <2026112002-CVE-2026-99701-3464@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=3004; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=U6syg5zsShQ+hIXWPtfbUEcu9TgQlczsrB4Ziz0LYcg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/73cx9uQpZwnK9nL8cF6j6ixYEeHidThtq5EJg+uvW b+zE3s6YlkYBJkYZMUUWb5s4zm6v+KQopeh7WmYOaxMIEMYuDgFYCLHRBjmx/VIFF9TrHB6a7Gg 7xR3P9fEbc9DGeYnO+dpB7096bdnxv8XbGLruvKDnTwB 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/ksm: fix userfaultfd protection during merge and unmerge KSM loses userfaultfd protection when replace_page() builds a new PTE from vma->vm_page_prot. Dropping its uffd bit lets a subsequent write go through ordinary COW instead of userfaultfd write protection handling. For RWP, a merged page also becomes readable without faulting. Keeping the uffd bit and restoring PAGE_NONE fixes merging, but we also have to handle unmerging. An existing KSM page can be protected with RWP before MADV_UNMERGEABLE, so unmerging already needs fixing independently of preserving RWP during merging. Unsharing replaces a shared page with a private one and should leave userfaultfd protection in place, as do_wp_page() already does for write protection. Currently, an unshare fault reaches do_uffd_rwp() before it can proceed to do_wp_page(). - With synchronous RWP, handle_userfault() returns VM_FAULT_SIGBUS. break_ksm() then reports success with a KSM page still merged. - With asynchronous RWP, protection is cleared before unsharing. Preserve the uffd bit when merging, and restore PAGE_NONE for RWP. Let FAULT_FLAG_UNSHARE skip RWP fault handling and keep PAGE_NONE on each private copy as well. Unsharing can then complete with RWP still armed for a subsequent access. The Linux kernel CVE team has assigned CVE-2026-99701 to this issue. Affected and fixed versions =========================== Issue introduced in 5.7 with commit 63b2d4174c4ad1f40b48d7138e71bcb564c1fe03 and fixed in 7.3.5 with commit 5cf7267b79f276c27825a2ebb95deda788a29e77 Issue introduced in 5.7 with commit 63b2d4174c4ad1f40b48d7138e71bcb564c1fe03 and fixed in 7.4-rc2 with commit 990d6c2194a938a19a8cf94c6cfd75171345089b 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-99701 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/ksm.c mm/memory.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/5cf7267b79f276c27825a2ebb95deda788a29e77 https://git.kernel.org/stable/c/990d6c2194a938a19a8cf94c6cfd75171345089b