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=1795154182; b=zPrg2BqpUx9UolK6BAGymxuNam7l+/C2cWLpckBQp5D7fWHEk7m7cywmd1I2lRNtFwSH k6uwmH2e+DJc/rttrcrmYPRwRCMPl6t/U9fvy/dneE0ckOpAN78YQmJZIDp/qA4iQ8Dg2 RmCfWpngsQ/aYMim7s4KSDXh8WzoQffRodP4oOqgBRdONve9rJ2ybshfg5c5/0t21XYdf 91DxJy654xwdFtWRdQApAnGUKLT/VwP3R17l0hdwwHJNeWSwKi5VOpFq3CvKBXi8X4gff nuX78zhbme9EUMO7YZT9vwgZO2eKSufBl4SCY0gCI8dDMUL3ARLpllxy98Iggkq4+mw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154182; 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=tZ6l4jJplFiJSu4uvzRNDzCoLA/xRchYvwcm5+gx5Cc=; b=X2zLKx/OlcXz6kDnIfuIOJuw5Ydq7bvpAb2nTAfe0KRfH7pNTHtL9vcc6+ZLCITfsEls M1+wkkw/s7CUmlz0Mz3FY8qqsAhBT823I4WTt826d40DALQqdyXMcAKGKbEQ5wI2QifMj t8TadVmuo86KpTqTJhzbRcB7UQ7dxekA55TuJ59QCTdxj6EYJRzobLNEms3RS51TU2YsG i0GahvcFWWGJg9Sw8BY+YMpfC40Au3JPYSIiFYZw9zSJbGPASACN3u5bIZbQbBHXx/LB6 DdfoPiMb13OsGMQgHHPYzzquU/vmQOVtnREUkx69dWiS/OijZm1c8CLUT23OOi6W04w== 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=ovgPxrja; 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 1BE4E606A320 for ; Fri, 20 Nov 2026 05:56:22 +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=ovgPxrja Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6C4481F000C6; Fri, 20 Nov 2026 05:56:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154182; bh=tZ6l4jJplFiJSu4uvzRNDzCoLA/xRchYvwcm5+gx5Cc=; h=From:To:Cc:Subject:Date:Reply-To; b=ovgPxrjaTAGjmzLFvEVzndw4REfRYBesDPPU0wcLjT1GIzEjYLbdJWSGbC35TIQH7 fyQLFtYT7Fqo3RRfUeMCFuAbATw2yYbLQkmvNA6AsrOcvwE9huWntEIZyjyG60pc7w GLog2tZ42Zpz/wGRryjiNhKhWuxkaTpTnxkqpW+w= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99654: mm: fix unmap_mapping_range() beyond 4 GiB on 32-bit Date: Fri, 20 Nov 2026 06:50:40 +0100 Message-ID: <2026112045-CVE-2026-99654-df0e@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=3919; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=U62duwjOy0yvoGwBvGAmVRtnSr3Bqtcljs8cKxcfdX4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/71d+FG7pX7tiGtsXxpv96V9nSlQ1nnnM56u64ErE1 NtBa1pvd8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBE4rYwzFNiZ3tSmqGQPFH+ gYvIee6yJx27/zLMZq1e9njm3+f/5fsS1D61TBM4vfPrZwA= 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 unmap_mapping_range() beyond 4 GiB on 32-bit Commit 9eab0421fa94 ("mm: fix unmap_mapping_range high bits shift bug") made holebegin and holelen unsigned before they are shifted, by casting them to pgoff_t. That is an unsigned long: on a 32-bit kernel the cast cuts off the upper half of the two loff_t values, so a hole which begins at 4 GiB or beyond is taken for one in the first 4 GiB of the file. truncate_pagecache() passes the new size of the file and asks for private COWed pages to be unmapped as well. If a file of 6 GiB is truncated to 5 GiB, everything from 1 GiB on is unmapped, and what a process has written to a private mapping of the range between 1 GiB and 5 GiB is lost: it reads the contents of the file again. Where the range has an end, the wrong range is unmapped instead of the right one. The page cache copes with that, as it unmaps every folio that it removes. The callers which only have unmap_mapping_range() to get rid of user mappings do not, for example drm_vma_node_unmap(), whose fake offsets reach beyond 4 GiB on 32-bit, and revoke_iomem() with physical addresses of more than 32 bits. Cast to u64 instead. Nothing changes for 64-bit kernels. Fix generated by an LLM and sent by Josef Bacik in private. The Linux kernel CVE team has assigned CVE-2026-99654 to this issue. Affected and fixed versions =========================== Issue introduced in 6.7 with commit 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d and fixed in 6.12.118 with commit cbf6c66a2ef46433092b41b87176755de32bf65b Issue introduced in 6.7 with commit 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d and fixed in 6.18.64 with commit 0cf8d3fdd869fe079e55f8e621e45397a819d93c Issue introduced in 6.7 with commit 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d and fixed in 7.3.5 with commit 67e6d5468a7d693a00176713d44267e5360d63c3 Issue introduced in 6.7 with commit 9eab0421fa94a3dde0d1f7e36ab3294fc306c99d and fixed in 7.4-rc2 with commit 7a81bc23dade8082187be6d9cc36e4be4b7207e2 Issue introduced in 4.19.305 with commit 2db1c46c3913b8bc92fed235a344de2671fe9d8d Issue introduced in 5.4.267 with commit 77359c4973056ba33a5627d5c04aea494eb76bc9 Issue introduced in 5.10.208 with commit 73704c6b35c7682fd22f97992a68b0e8451c7a52 Issue introduced in 5.15.147 with commit 91432aebce514cab49f63324c98b4eccb80532c5 Issue introduced in 6.1.72 with commit dafdeb7b91f1597983693a418c496b6702ea34b5 Issue introduced in 6.6.11 with commit 2247df454c7bb4b13939794fe6fae8510868d241 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-99654 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/cbf6c66a2ef46433092b41b87176755de32bf65b https://git.kernel.org/stable/c/0cf8d3fdd869fe079e55f8e621e45397a819d93c https://git.kernel.org/stable/c/67e6d5468a7d693a00176713d44267e5360d63c3 https://git.kernel.org/stable/c/7a81bc23dade8082187be6d9cc36e4be4b7207e2