From: steven chen <chenste@linux.microsoft.com>
To: zohar@linux.ibm.com, stefanb@linux.ibm.com,
roberto.sassu@huaweicloud.com, petr@tesarici.cz,
eric.snowberg@oracle.com, paul@paul-moore.com, code@tyhicks.com,
nramas@linux.microsoft.com,
James.Bottomley@HansenPartnership.com,
madvenka@linux.microsoft.com
Cc: linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, chenste@linux.microsoft.com
Subject: [PATCH v6 3/7] ima: kexec: skip IMA segment validation after kexec soft reboot
Date: Fri, 24 Jan 2025 14:55:43 -0800 [thread overview]
Message-ID: <20250124225547.22684-4-chenste@linux.microsoft.com> (raw)
In-Reply-To: <20250124225547.22684-1-chenste@linux.microsoft.com>
kexec_calculate_store_digests() calculates and stores the digest of the
segment at kexec_file_load syscall where the IMA segment is also
allocated. With this series, the IMA segment will be updated with the
measurement log at kexec soft reboot. Therefore, it may fail digest
verification in verify_sha256_digest() after kexec soft reboot into the
new Kernel. Therefore, the digest calculation/verification of the IMA
segment needs to be skipped.
Skip IMA segment from calculating and storing digest in function
kexec_calculate_store_digests() so that it is not added to the
'purgatory_sha_regions'.
Since verify_sha256_digest() only verifies 'purgatory_sha_regions',
no change is needed in verify_sha256_digest() in this context.
With this change, the IMA segment is not included in the digest
calculation, storage, and verification.
Author: Tushar Sugandhi <tusharsu@linux.microsoft.com>
Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
Signed-off-by: steven chen <chenste@linux.microsoft.com>
---
include/linux/kexec.h | 3 +++
kernel/kexec_file.c | 10 ++++++++++
security/integrity/ima/ima_kexec.c | 3 +++
3 files changed, 16 insertions(+)
diff --git a/include/linux/kexec.h b/include/linux/kexec.h
index f8413ea5c8c8..f3246e881ac8 100644
--- a/include/linux/kexec.h
+++ b/include/linux/kexec.h
@@ -362,6 +362,9 @@ struct kimage {
phys_addr_t ima_buffer_addr;
size_t ima_buffer_size;
+
+ unsigned long ima_segment_index;
+ bool is_ima_segment_index_set;
#endif
/* Core ELF header buffer */
diff --git a/kernel/kexec_file.c b/kernel/kexec_file.c
index 3eedb8c226ad..4ff3ba0f3e8e 100644
--- a/kernel/kexec_file.c
+++ b/kernel/kexec_file.c
@@ -764,6 +764,16 @@ static int kexec_calculate_store_digests(struct kimage *image)
if (ksegment->kbuf == pi->purgatory_buf)
continue;
+#ifdef CONFIG_IMA_KEXEC
+ /*
+ * Skip the segment if ima_segment_index is set and matches
+ * the current index
+ */
+ if (image->is_ima_segment_index_set &&
+ i == image->ima_segment_index)
+ continue;
+#endif
+
ret = crypto_shash_update(desc, ksegment->kbuf,
ksegment->bufsz);
if (ret)
diff --git a/security/integrity/ima/ima_kexec.c b/security/integrity/ima/ima_kexec.c
index b60a902460e2..283860d20521 100644
--- a/security/integrity/ima/ima_kexec.c
+++ b/security/integrity/ima/ima_kexec.c
@@ -162,6 +162,7 @@ void ima_add_kexec_buffer(struct kimage *image)
kbuf.buffer = kexec_buffer;
kbuf.bufsz = kexec_buffer_size;
kbuf.memsz = kexec_segment_size;
+ image->is_ima_segment_index_set = false;
ret = kexec_add_buffer(&kbuf);
if (ret) {
pr_err("Error passing over kexec measurement buffer.\n");
@@ -172,6 +173,8 @@ void ima_add_kexec_buffer(struct kimage *image)
image->ima_buffer_addr = kbuf.mem;
image->ima_buffer_size = kexec_segment_size;
image->ima_buffer = kexec_buffer;
+ image->ima_segment_index = image->nr_segments - 1;
+ image->is_ima_segment_index_set = true;
/*
* kexec owns kexec_buffer after kexec_add_buffer() is called
--
2.25.1
next prev parent reply other threads:[~2025-01-24 22:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 22:55 [PATCH v6 0/7] ima: kexec: measure events between kexec load and excute steven chen
2025-01-24 22:55 ` [PATCH v6 1/7] ima: define and call ima_alloc_kexec_file_buf steven chen
2025-01-24 22:55 ` [PATCH v6 2/7] kexec: define functions to map and unmap segments steven chen
2025-01-24 22:55 ` steven chen [this message]
2025-01-28 15:23 ` [PATCH v6 3/7] ima: kexec: skip IMA segment validation after kexec soft reboot Stefan Berger
2025-01-29 17:58 ` steven chen
2025-01-24 22:55 ` [PATCH v6 4/7] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-01-24 22:55 ` [PATCH v6 5/7] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-01-24 22:55 ` [PATCH v6 6/7] ima: make the kexec extra memory configurable steven chen
2025-01-28 15:18 ` Stefan Berger
2025-01-28 18:34 ` steven chen
2025-01-24 22:55 ` [PATCH 7/7] ima: measure kexec load and exec events as critical data steven chen
2025-01-28 15:28 ` Stefan Berger
2025-01-28 17:29 ` Stefan Berger
2025-01-28 18:35 ` steven chen
-- strict thread matches above, loose matches on Subject: below --
2025-01-24 22:42 [PATCH v6 0/7] *** SUBJECT HERE *** steven chen
2025-01-24 22:42 ` [PATCH v6 3/7] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250124225547.22684-4-chenste@linux.microsoft.com \
--to=chenste@linux.microsoft.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=code@tyhicks.com \
--cc=eric.snowberg@oracle.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=nramas@linux.microsoft.com \
--cc=paul@paul-moore.com \
--cc=petr@tesarici.cz \
--cc=roberto.sassu@huaweicloud.com \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).