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=1795057491; b=XioEKWZ+WmITdtyqAhxiHvfHsSajxsn+n2zimcThD0NyDoEcd1iptzLi6QLBtqtAb1i8 vYTG7C5vlbsBV6wmoyOgVWy5r6tDHianyHwEAcgF8ZkVgnq4uQUrv1YgyGQO7VmAb4PCv oVJQBu6hvKitKcZ2eV9ddso+T2Dk0lQV8as5xzt5uz/XZrguT8fz/xa/vc3EYpLoc4Qfz EvOn60FVK3gEKq3ofyNW+4Ppo7tUnL+TrfnXm3hYq1USzXnJ5dQHrMcd/d+12JGh8b7MP 1ePIXKs6WDeRVvhkcjAmQQ/aKOrBlffW0JVbhtDKnhIP8Q9DGWzsC+aKUj8zxK8Tv+A== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795057491; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:User-Agent:X-stable:X-Patchwork-Hint: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=2pRQPRlKT5eBxtPJ8Es5AoF431BcGO5YNQkVnun6xxU=; b=jt/6sVA3u3VLX3bOJXOXWBzb3fNroYeITMPLPMZI5nfJYoXtjAjMdNe7RLS2bXcnOhLJ AHoDDIPiY7F0CWVCja9QWlacGeeU+sYdj93Duoj+HlcW3x6D7EhxzvdzoCIwZpK3suETi 7yoSTapUgcpyfyS1IUj62+cw/DHqr8GDuOVHgcOk0iNft+lHE8sZeMg9w/D5CoIt1rcrw WnGWk+YB+bh0oSaCoWGNzmbzlKjoyqdiWv0MsOYJN+k6idEpB7kivs0Hjoc8x2itOoYUs Ggdony+GrqRKaWqqu/cdewIJasFUvj1BZsWbxAJOnj/lFqA42RPjKVMAeBjth7HrWlw== 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=b0e8OInL; 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 A769E606A31C; Thu, 19 Nov 2026 03:04:51 +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=b0e8OInL Received: by smtp.kernel.org (Postfix) with ESMTPSA id 054361F000C4; Thu, 19 Nov 2026 03:04:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795057491; bh=2pRQPRlKT5eBxtPJ8Es5AoF431BcGO5YNQkVnun6xxU=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=b0e8OInL2K9b4dSlJfIZB2JucDSykGubPx1IQTiZK2Taout4Dg/77562ED6B3nmwF 3IjIjM3XtqdffNP+u+7L1vfA+fShEoS7scZ6l2/IX9Qzugc5Palt/TDIru/oS53cCG c18+rly3aevASXkfjma0JxWo3HMmP0lqklvkj1ME= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, liulhong617 , Will Deacon , Sasha Levin Subject: [PATCH 5.10 0150/1848] arm64: mm: fix accidental linear mapping of no-map reserved memory Date: Wed, 18 Nov 2026 15:36:28 +0100 Message-ID: <20261118145917.529160369@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261118145911.150052362@linuxfoundation.org> References: <20261118145911.150052362@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore X-Mailing-List: patches@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 5.10-stable review patch. If anyone has any objections, please let me know. ------------------ From: liulhong617 [ Upstream commit 7ace06a01efaba1ec585630aa4c98ac39b38452a ] When reserved-memory regions with the "no-map" property are not page-aligned, the kernel may accidentally map them into the linear mapping, contradicting the no-map semantics. The root cause is a mismatch between /proc/iomem's address boundaries and the actual page table mapping boundaries: 1. /proc/iomem derives its ranges from memblock via memblock_region_reserved_base_pfn/memblock_region_reserved_end_pfn, which perform PFN rounding so the displayed boundaries are page-aligned. This gives the impression that the no-map region occupies whole pages. 2. However, memblock_mark_nomap() splits memblock.memory regions at exact byte boundaries (memblock_isolate_range preserves raw DT base/size with no alignment). When for_each_mem_range iterates the non-NOMAP regions adjacent to a no-map region, it returns start/end values that are NOT page-aligned — they are the precise byte boundaries from the memblock split. 3. These sub-page-aligned values are passed to __create_pgd_mapping_locked(), which does: phys &= PAGE_MASK; addr = virt & PAGE_MASK; end = PAGE_ALIGN(virt + size); The downward rounding of phys via PAGE_MASK extends the mapped range backward into the adjacent no-map region, effectively including no-map memory in the linear mapping. For example, with 64K pages, reserved_region@A2000000 (base=0xA2000000, size=0x8000, no-map) causes for_each_mem_range to return start=0xA2008000 for the next mappable region. After phys &= PAGE_MASK, the actual mapping starts at 0xA2000000 — the entire no-map region is incorrectly mapped. Fix this by rounding the mappable range inward to PAGE_SIZE boundaries before passing it to __map_memblock: start is rounded UP and end is rounded DOWN. This ensures the mapped area never overlaps with adjacent no-map regions. The cost is at most one page of unmapped gap at each boundary, which is preferable to violating no-map semantics. Signed-off-by: liulhong617 Signed-off-by: Will Deacon Signed-off-by: Sasha Levin --- arch/arm64/mm/mmu.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c index ff16cc7251b40..cf4d293e9fe61 100644 --- a/arch/arm64/mm/mmu.c +++ b/arch/arm64/mm/mmu.c @@ -527,6 +527,20 @@ static void __init map_mem(pgd_t *pgdp) for_each_mem_range(i, &start, &end) { if (start >= end) break; + /* + * for_each_mem_range may return sub-page-aligned boundaries + * after memblock_mark_nomap() splits regions at byte precision. + * __create_pgd_mapping_locked aligns phys down to PAGE_MASK, + * which could accidentally map no-map memory on the boundary. + * Round the mappable range inward: start UP, end DOWN, so + * that the mapped area never overlaps with adjacent no-map + * regions. The cost is at most one page of unmapped gap at + * each boundary. + */ + start = PAGE_ALIGN(start); + end = end & PAGE_MASK; + if (start >= end) + continue; /* * The linear map must allow allocation tags reading/writing * if MTE is present. Otherwise, it has the same attributes as -- 2.53.0