From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from m16.mail.163.com (m16.mail.163.com [220.197.31.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D187947F2E6; Wed, 3 Jun 2026 13:05:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=220.197.31.4 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780491921; cv=none; b=qTDbz+BbM1yEHcD9Wpp5szq8Vo1EOAS6dz47je+X1XPgtRTtZXQUzUoKfjI6tj4z2+583ZJJZdtoi547Qe+pH1TRrA11sEBXKi9qSXFR6pfkE+JL/UTqMO4D6BjDuu1z0qkhTlmkS5/zzPp7lu7S2mgndxIbQxzCOPEf/3PRy+I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780491921; c=relaxed/simple; bh=4KDNC+n7Zn9Ap+bf3UhGe7DONQsTBW8GrIAi5N4qrR4=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=Un0PnwQ5SxOSYv+ikkOIjPArWJrbDCEPN4ezdwoy8beEHnGEEKl/uq+jXnfdHIlcSiGZtGQ7aeNIleiz2GV675ZMrJWP+jCF3rgWRbhY9lBHBHwkHUA8k3eTDqKHX8ndAkVuAviaHYhD/dvtV14/5QKjNpysiIm5BvMmM2iGMjc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=163.com; spf=pass smtp.mailfrom=163.com; dkim=pass (1024-bit key) header.d=163.com header.i=@163.com header.b=NoguVVMF; arc=none smtp.client-ip=220.197.31.4 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=163.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=163.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=163.com header.i=@163.com header.b="NoguVVMF" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; bh=bLLBHy12NTJHyuPLkj8zZD9oFwdYVG8GLqwIPAHIL+M=; b=NoguVVMFrLYHHWSXCA9/8JuSbWcp/nOaP0/r2kz45BxyER6D1c3ROt9C8lmKnK msn8ZA8/BHr0NDKyvUc8GVCzLsvQQJBuQ4bnjqHmx1qGPXz0YBMnuIe5zxTPBr6/ lzcUi0wCvZ0bHpoAA35sog2nc4IA8ETqGhsi4WFddJyDw= Received: from China-163-team (unknown []) by gzga-smtp-mtada-g0-4 (Coremail) with SMTP id _____wBnoqAAJiBqWd71BA--.49866S4; Wed, 03 Jun 2026 21:03:15 +0800 (CST) From: Wenshan Lan To: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Harshit Mogalapalli , Paul Webb , Mimi Zohar , Alexander Graf , Ard Biesheuvel , Baoquan He , Borislav Betkov , guoweikang , Henry Willard , "H. Peter Anvin" , Ingo Molnar , Jiri Bohac , Joel Granados , Jonathan McDowell , Mike Rapoport , Sohil Mehta , Sourabh Jain , Thomas Gleinxer , Yifei Liu , Andrew Morton , Wenshan Lan Subject: [PATCH 6.6.y 3/3] x86/kexec: add a sanity check on previous kernel's ima kexec buffer Date: Wed, 3 Jun 2026 21:02:39 +0800 Message-ID: <20260603130239.81400-3-jetlan9@163.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20260603130239.81400-1-jetlan9@163.com> References: <20260603130239.81400-1-jetlan9@163.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-CM-TRANSID:_____wBnoqAAJiBqWd71BA--.49866S4 X-Coremail-Antispam: 1Uf129KBjvJXoWxXFWUAF18tF1rZF4UXw4Dtwb_yoW5Gw47p3 9I9r48GrnrJ3WxGw18CryUuas8ZaykWF1UWF4Dur93Ar15tr17XrsYvF1xZF42vFWrKFyr J3Wjgw1Fg3yUXaDanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x0ziyrWrUUUUU= X-CM-SenderInfo: xmhwztjqz6il2tof0z/xtbCxBMw+GogJhNt6QAA3k From: Harshit Mogalapalli [ Upstream commit c5489d04337b47e93c0623e8145fcba3f5739efd ] When the second-stage kernel is booted via kexec with a limiting command line such as "mem=", the physical range that contains the carried over IMA measurement list may fall outside the truncated RAM leading to a kernel panic. BUG: unable to handle page fault for address: ffff97793ff47000 RIP: ima_restore_measurement_list+0xdc/0x45a #PF: error_code(0x0000) – not-present page Other architectures already validate the range with page_is_ram(), as done in commit cbf9c4b9617b ("of: check previous kernel's ima-kexec-buffer against memory bounds") do a similar check on x86. Without carrying the measurement list across kexec, the attestation would fail. Link: https://lkml.kernel.org/r/20251231061609.907170-4-harshit.m.mogalapalli@oracle.com Signed-off-by: Harshit Mogalapalli Fixes: b69a2afd5afc ("x86/kexec: Carry forward IMA measurement log on kexec") Reported-by: Paul Webb Reviewed-by: Mimi Zohar Cc: Alexander Graf Cc: Ard Biesheuvel Cc: Baoquan He Cc: Borislav Betkov Cc: guoweikang Cc: Henry Willard Cc: "H. Peter Anvin" Cc: Ingo Molnar Cc: Jiri Bohac Cc: Joel Granados Cc: Jonathan McDowell Cc: Mike Rapoport Cc: Sohil Mehta Cc: Sourabh Jain Cc: Thomas Gleinxer Cc: Yifei Liu Cc: Signed-off-by: Andrew Morton Signed-off-by: Wenshan Lan --- arch/x86/kernel/setup.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c index eb129277dcdd..df74f865c9f1 100644 --- a/arch/x86/kernel/setup.c +++ b/arch/x86/kernel/setup.c @@ -372,9 +372,15 @@ int __init ima_free_kexec_buffer(void) int __init ima_get_kexec_buffer(void **addr, size_t *size) { + int ret; + if (!ima_kexec_buffer_size) return -ENOENT; + ret = ima_validate_range(ima_kexec_buffer_phys, ima_kexec_buffer_size); + if (ret) + return ret; + *addr = __va(ima_kexec_buffer_phys); *size = ima_kexec_buffer_size; -- 2.43.0