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=1795154184; b=45jI6A/9qeRDp06cUjYz+VmtXc8nVQaA7EmlRG/9Km5LQ1yslZQ2IrsjrzgvYXFxjmMe PLcB0Ds+h0Quymf3CQ/kzDYAvwivCyyqtQ4yusWsM8GhMToTjNv5YQnj0M+UE5JGudmWw ulpDGiQA/ofApqcCjAbvRb8rJbw02KPamDfxaBL+CplU6AC1dfYDERpBR1mUEtDnMXvpm tQwQMheH6V0CP1BMHBhGeXIivVTjR3JVKWpONot+AV43LUTqHfqsiT0dJt147jgzFw4w0 CXjsGC8UunSWm9s8dwxC0cLS/CpJ9naUXcM/WuzpC3dGCFyf9cDYqwbfpzIDd0UGxjg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154184; 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=gmdzmdTnGj2tVjfH3uHxHzuIRoNbNAe8yChs4XePZzE=; b=xXHeVa8h2JlToXfWC/qFokUBPjZkUYP95Nv1AYzGhKqzE3TxH9+o1oNSeboftNqRCqZS TMDCHPotAVR1/LLoiqHQb7nYg2eCwqpn9An78IdM1uAPFar3ZKYCvDeoHJLch3Bu6UT6e v/SnQ5FnFGKppJYIgvSaBumxJMELX0C1fOEuu5cxNXh5t04Hi4Uq1Ow+qwIcTx7c29uq1 OpjiCYdCJuSHLAkWheHaDt/0oWoHv5HPlycKwOPuQAd9JAKihGqCNlu5HQAgUcuf3B2Ic EhjNmq5AbtF5ClOjkkMmNKNhZCD5plahauDtD3ydy4sOWlU7iuT6FsLS6hUeoLFiNxQ== 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=jtreZc4I; 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 DB0FB606A320 for ; Fri, 20 Nov 2026 05:56:24 +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=jtreZc4I Received: by smtp.kernel.org (Postfix) with ESMTPSA id 373D61F000C6; Fri, 20 Nov 2026 05:56:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154184; bh=gmdzmdTnGj2tVjfH3uHxHzuIRoNbNAe8yChs4XePZzE=; h=From:To:Cc:Subject:Date:Reply-To; b=jtreZc4IGYlJ1Au5F5+vPm96vWcBmAtrhHlXmHXh1OGS9Fmvqwy4G6fp3sF6DifrU rZ7CoAi3vIKlwiDw6tkHi1c2PJts99wLCfd3lpjQSy+XAj8E4B2+FnA6gshK4D8BWV bpbhybYlDuP2XPY2RzQdfNr8l6Vwz8Q0uo/btPhY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99655: mm/memory: reject remote COW faults on PFN mappings Date: Fri, 20 Nov 2026 06:50:41 +0100 Message-ID: <2026112045-CVE-2026-99655-a051@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=3236; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=H5YcO4ae28efziTVYTgk5yef5PLrn3dWDZpQ9zhDPpo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/71em7dBe+t7EdFvKiuyQhdGlE1X0Ba5+8JupWzrz2 64w9+K9HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRX9sZ5lkIXrf3/bj2RLfb +9brgbdNzl0w1WCYw3ElsLHtLIu10J4/W7siRJYtcRCcDAA= 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/memory: reject remote COW faults on PFN mappings When handling a COW fault without a normal source page (PFN mappings), __wp_page_copy_user() copies from the faulting user address. For remote faults, this accesses the wrong address space, resulting in wrong data getting copied. For example, user_events updates an enable bit in the registering process's memory. If that memory needs to be faulted in, user_event_enabler_fault_fixup() calls fixup_user_fault() from a work item. Placing the enable bit in a private PFN mapping can trigger this remote COW path. Reject these faults with VM_FAULT_SIGBUS when the target mm differs from current->mm: remote faults. Ordinary (non-PFN) mappings are not affected. The user-address copy dates back to commit 6aab341e0a28 ("mm: re-architect the VM_UNPAGED logic"); likely, actual ways to get remote faults in there on COW PFN mappings appeared afterwards. But the fix is simple and straight forward. Fix generated by an LLM and sent by Chris Mason in private. [ david: simplify comment and description ] The Linux kernel CVE team has assigned CVE-2026-99655 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.15 with commit 6aab341e0a28aff100a09831c5300a2994b8b986 and fixed in 6.12.118 with commit dd273e2d8d20f681a0147f13c12a1eb748fb9621 Issue introduced in 2.6.15 with commit 6aab341e0a28aff100a09831c5300a2994b8b986 and fixed in 6.18.64 with commit 27b2e29733a837552f0f31370e9066fa28466353 Issue introduced in 2.6.15 with commit 6aab341e0a28aff100a09831c5300a2994b8b986 and fixed in 7.3.5 with commit 649937cf1df6c70b8e5b0cd13a34945c547235d1 Issue introduced in 2.6.15 with commit 6aab341e0a28aff100a09831c5300a2994b8b986 and fixed in 7.4-rc2 with commit 8db6921cc07b74197a3866d62ed262b68aeadcf3 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-99655 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/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/dd273e2d8d20f681a0147f13c12a1eb748fb9621 https://git.kernel.org/stable/c/27b2e29733a837552f0f31370e9066fa28466353 https://git.kernel.org/stable/c/649937cf1df6c70b8e5b0cd13a34945c547235d1 https://git.kernel.org/stable/c/8db6921cc07b74197a3866d62ed262b68aeadcf3