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=1795154163; b=WWAVo0sLFcMgCV2q6GQBolOkIziWHlyNEN/ccsTV9FEN6SW+BitLWS9SEQ0RCQseCtY+ FQBrSNWfxCl5t8HCIwxKBDjW4Kbjr+cW+dsQRYv4J4Ri+ofraY2NU9T7GXmaRheOtggkL 1gLlW/NE8KDfL0qWxuBiK4kQJ3PPmaYg2ZcLrwzC0JGPF1PJXu0dzBICUt/iitJ6Tu9kQ HnAFM28vVaVvjXFXvqGYbXb22yynZqvcGbT+2IHkr8HrkXFgZ1oNxJezyu6qznxZ7TlpA 3YGRHOeEbvix7+IQ00ZqudJ40/7S5ThDi8MZhMA/t9LFjDpp+ty13giRxo8Ss+7Yw8A== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154163; 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=jXpH1mNgZ7zYBXo8BGgPfWbv81LMW9Aa8zThPqSjX+k=; b=OdT8aGi5uRixCs7vNXQN6kuECzL08X02Bj8P3bZ7ozqBpxwWzHRC46evfziU7gq4JawS R/P4HiU+xE1QeVcimmS96Qd/qnS612WC2xu8gVHM8zYOYN6S5ROXmANjIxFs/Hqm0fQya Tez0GWn+VQmly2xQxrRytqu+F+qQ4eK/+UcQoQtMHhyvUWjmR//EmQ0D3HgR8nbUvmEpD l7qn4jOHYdltbx0qWQ39SwjPdiEKivVPK4WmbXMnb2imRDngjMDJEmhtvYcVOW35uQlz8 M9O7PlarV8itbx02ilufSZuXmnXlPD9RY/BSTpwjwC/L57Anfojk+IfoCDJ/cUoHkIQ== 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=P2LBguW7; 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 49FEE606A320 for ; Fri, 20 Nov 2026 05:56:02 +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=P2LBguW7 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 93CAF1F000C4; Fri, 20 Nov 2026 05:56:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154162; bh=jXpH1mNgZ7zYBXo8BGgPfWbv81LMW9Aa8zThPqSjX+k=; h=From:To:Cc:Subject:Date:Reply-To; b=P2LBguW70yj1SCGbKGr5R0wqQSrS2/sic2i3y9CDY5MLpBmcobRW0+sRDJ3/LgCUw 4GazMVZOTXSYg2q8sIRvwa9bS7r0XqC0rgx2IYkBY/QW+IdjUJzDrsqqzCACRKnSPH n58Ghjye5xPJBhPTexEiPdf0r5QlrrS+Cltuq/04= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99648: mm/vma: call ->may_split() before a partial merge Date: Fri, 20 Nov 2026 06:50:34 +0100 Message-ID: <2026112043-CVE-2026-99648-2e53@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=4105; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=pjZKX2jGKYOkaPr6uvnfMTViPvXEJ+Ya0HnJSLjRe40=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/75d/zrd5uCGF7fBaNvGnfke6mhqftLslmTv8/85y/ mX11avtHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCReTMYFizWi8+y++K+sX7n 2+rU5SGPAna6LGaY77NTb0pdl5e/cc06O+VPG9M4E79oAAA= 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/vma: call ->may_split() before a partial merge A driver can use the ->may_split() hook to forbid a VMA boundary at certain addresses. A device-dax device is a character device that gives raw access to a range of memory through mmap(). device-dax refuses any address that is not a multiple of the device's alignment through vm_ops->may_split. vma_merge_existing_range() can move boundaries, but does not call vm_ops->may_split. If a range at the edge of a VMA gets the attributes of the adjacent VMA, the function moves only that range over to the neighbour: one VMA shrinks and the other grows. This is a partial merge, and vma_modify() tries it before any split. Take a device-dax VMA that lies next to another VMA of the same file. The user calls mprotect() on the one page of the first VMA that touches the second VMA, and asks for the protection that the second VMA already has. The result is a partial merge. It puts the boundary inside a 1 GiB mapping, which is a single leaf entry at the PUD level. As part of the merge, the kernel looks for a huge PMD to split at the new boundary. That code does not expect a PUD leaf: vma_merge_existing_range() commit_merge() vma_adjust_trans_huge() split_huge_pmd_address() mm_find_pmd() treats the PUD leaf as a pointer to a PMD table, so the "table" is the device memory that the leaf maps __split_huge_pmd() reads a PMD that the user wrote to the device memory folio_put() on the folio that this PMD names Bad. While the code must at some point be taught to split PUD entries as well, the issue here is that we move VMA boundaries such that they are incompatible with the driver. Fix this by calling ->may_split() on the address that a partial merge would move the boundary to, and by abandoning the merge if the driver refuses. vma_modify() then tries the split, which fails with -EINVAL. Factor out existing split handling into check_split() and reuse it. Fix generated by an LLM and sent by Chris Mason in private. [ david: improve description; cleanup the code ] The Linux kernel CVE team has assigned CVE-2026-99648 to this issue. Affected and fixed versions =========================== Issue introduced in 6.15 with commit 38607c62b34b46317c46d5baf1df03ac6e48a1c6 and fixed in 6.18.64 with commit f437fcb76d448a396940498aba278ac0ad8d715a Issue introduced in 6.15 with commit 38607c62b34b46317c46d5baf1df03ac6e48a1c6 and fixed in 7.3.5 with commit 456932cdc6eda70b5ad4c628556098846699ab03 Issue introduced in 6.15 with commit 38607c62b34b46317c46d5baf1df03ac6e48a1c6 and fixed in 7.4-rc2 with commit 0193e83368022a308d19ee0293f55a4f5d548e40 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-99648 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/vma.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/f437fcb76d448a396940498aba278ac0ad8d715a https://git.kernel.org/stable/c/456932cdc6eda70b5ad4c628556098846699ab03 https://git.kernel.org/stable/c/0193e83368022a308d19ee0293f55a4f5d548e40