From: Baoquan He <bhe@redhat.com>
To: steven chen <chenste@linux.microsoft.com>
Cc: zohar@linux.ibm.com, stefanb@linux.ibm.com,
roberto.sassu@huaweicloud.com, roberto.sassu@huawei.com,
eric.snowberg@oracle.com, ebiederm@xmission.com,
paul@paul-moore.com, code@tyhicks.com, bauermann@kolabnow.com,
linux-integrity@vger.kernel.org, kexec@lists.infradead.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, madvenka@linux.microsoft.com,
nramas@linux.microsoft.com,
James.Bottomley@hansenpartnership.com, vgoyal@redhat.com,
dyoung@redhat.com
Subject: Re: [PATCH v12 9/9] ima: measure kexec load and exec events as critical data
Date: Fri, 18 Apr 2025 17:08:03 +0800 [thread overview]
Message-ID: <aAIWcwzuht+GCn29@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20250416021028.1403-10-chenste@linux.microsoft.com>
On 04/15/25 at 07:10pm, steven chen wrote:
> From: Steven Chen <chenste@linux.microsoft.com>
>
> The amount of memory allocated at kexec load, even with the extra memory
> allocated, might not be large enough for the entire measurement list. The
> indeterminate interval between kexec 'load' and 'execute' could exacerbate
> this problem.
>
> Define two new IMA events, 'kexec_load' and 'kexec_execute', to be
> measured as critical data at kexec 'load' and 'execute' respectively.
> Report the allocated kexec segment size, IMA binary log size and the
> runtime measurements count as part of those events.
>
> These events, and the values reported through them, serve as markers in
> the IMA log to verify the IMA events are captured during kexec soft
> reboot. The presence of a 'kexec_load' event in between the last two
> 'boot_aggregate' events in the IMA log implies this is a kexec soft
> reboot, and not a cold-boot. And the absence of 'kexec_execute' event
> after kexec soft reboot implies missing events in that window which
> results in inconsistency with TPM PCR quotes, necessitating a cold boot
> for a successful remote attestation.
>
> These critical data events are displayed as hex encoded ascii in the
> ascii_runtime_measurement_list. Verifying the critical data hash requires
> calculating the hash of the decoded ascii string.
>
> For example, to verify the 'kexec_load' data hash:
>
> sudo cat /sys/kernel/security/integrity/ima/ascii_runtime_measurements
> | grep kexec_load | cut -d' ' -f 6 | xxd -r -p | sha256sum
>
>
> To verify the 'kexec_execute' data hash:
>
> sudo cat /sys/kernel/security/integrity/ima/ascii_runtime_measurements
> | grep kexec_execute | cut -d' ' -f 6 | xxd -r -p | sha256sum
>
> Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
^^^^^
> Signed-off-by: Steven Chen <chenste@linux.microsoft.com>
^^^^^
> Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
> ---
> security/integrity/ima/ima.h | 6 ++++++
> security/integrity/ima/ima_kexec.c | 21 +++++++++++++++++++++
> security/integrity/ima/ima_queue.c | 5 +++++
> 3 files changed, 32 insertions(+)
Acked-by: Baoquan He <bhe@redhat.com>
>
> diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h
> index 24d09ea91b87..34815baf5e21 100644
> --- a/security/integrity/ima/ima.h
> +++ b/security/integrity/ima/ima.h
> @@ -240,6 +240,12 @@ void ima_post_key_create_or_update(struct key *keyring, struct key *key,
> unsigned long flags, bool create);
> #endif
>
> +#ifdef CONFIG_IMA_KEXEC
> +void ima_measure_kexec_event(const char *event_name);
> +#else
> +static inline void ima_measure_kexec_event(const char *event_name) {}
> +#endif
> +
> /*
> * The default binary_runtime_measurements list format is defined as the
> * platform native format. The canonical format is defined as little-endian.
> diff --git a/security/integrity/ima/ima_kexec.c b/security/integrity/ima/ima_kexec.c
> index d1c9d369ba08..38cb2500f4c3 100644
> --- a/security/integrity/ima/ima_kexec.c
> +++ b/security/integrity/ima/ima_kexec.c
> @@ -17,6 +17,8 @@
> #include "ima.h"
>
> #ifdef CONFIG_IMA_KEXEC
> +#define IMA_KEXEC_EVENT_LEN 256
> +
> static bool ima_kexec_update_registered;
> static struct seq_file ima_kexec_file;
> static size_t kexec_segment_size;
> @@ -31,6 +33,24 @@ static void ima_free_kexec_file_buf(struct seq_file *sf)
> sf->count = 0;
> }
>
> +void ima_measure_kexec_event(const char *event_name)
> +{
> + char ima_kexec_event[IMA_KEXEC_EVENT_LEN];
> + size_t buf_size = 0;
> + long len;
> + int n;
> +
> + buf_size = ima_get_binary_runtime_size();
> + len = atomic_long_read(&ima_htable.len);
> +
> + n = scnprintf(ima_kexec_event, IMA_KEXEC_EVENT_LEN,
> + "kexec_segment_size=%lu;ima_binary_runtime_size=%lu;"
> + "ima_runtime_measurements_count=%ld;",
> + kexec_segment_size, buf_size, len);
> +
> + ima_measure_critical_data("ima_kexec", event_name, ima_kexec_event, n, false, NULL, 0);
> +}
> +
> static int ima_alloc_kexec_file_buf(size_t segment_size)
> {
> /*
> @@ -53,6 +73,7 @@ static int ima_alloc_kexec_file_buf(size_t segment_size)
> out:
> ima_kexec_file.read_pos = 0;
> ima_kexec_file.count = sizeof(struct ima_kexec_hdr); /* reserved space */
> + ima_measure_kexec_event("kexec_load");
>
> return 0;
> }
> diff --git a/security/integrity/ima/ima_queue.c b/security/integrity/ima/ima_queue.c
> index 83d53824aa98..590637e81ad1 100644
> --- a/security/integrity/ima/ima_queue.c
> +++ b/security/integrity/ima/ima_queue.c
> @@ -241,6 +241,11 @@ static int ima_reboot_notifier(struct notifier_block *nb,
> unsigned long action,
> void *data)
> {
> +#ifdef CONFIG_IMA_KEXEC
> + if (action == SYS_RESTART && data && !strcmp(data, "kexec reboot"))
> + ima_measure_kexec_event("kexec_execute");
> +#endif
> +
> ima_measurements_suspend();
>
> return NOTIFY_DONE;
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-04-18 9:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 2:10 [PATCH v12 0/9] ima: kexec: measure events between kexec load and execute steven chen
2025-04-16 2:10 ` [PATCH v12 1/9] ima: rename variable the seq_file "file" to "ima_kexec_file" steven chen
2025-04-18 3:30 ` Baoquan He
2025-04-16 2:10 ` [PATCH v12 2/9] ima: define and call ima_alloc_kexec_file_buf() steven chen
2025-04-18 4:33 ` Baoquan He
2025-04-20 12:22 ` steven chen
2025-04-16 2:10 ` [PATCH v12 3/9] kexec: define functions to map and unmap segments steven chen
2025-04-18 4:36 ` Baoquan He
2025-04-20 12:30 ` steven chen
2025-04-21 2:09 ` Baoquan He
2025-04-21 13:51 ` Mimi Zohar
2025-04-21 14:18 ` Mimi Zohar
2025-04-21 20:40 ` steven chen
2025-04-21 21:35 ` Mimi Zohar
2025-04-21 21:44 ` steven chen
2025-04-16 2:10 ` [PATCH v12 4/9] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
2025-04-18 7:37 ` Baoquan He
2025-04-20 12:32 ` steven chen
2025-04-16 2:10 ` [PATCH v12 5/9] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-04-18 7:40 ` Baoquan He
2025-04-20 12:33 ` steven chen
2025-04-16 2:10 ` [PATCH v12 6/9] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-04-16 2:10 ` [PATCH v12 7/9] ima: verify if the segment size has changed steven chen
2025-04-16 2:10 ` [PATCH v12 8/9] ima: make the kexec extra memory configurable steven chen
2025-04-18 8:14 ` Baoquan He
2025-04-20 13:03 ` steven chen
2025-04-16 2:10 ` [PATCH v12 9/9] ima: measure kexec load and exec events as critical data steven chen
2025-04-18 9:08 ` Baoquan He [this message]
2025-04-20 13:10 ` steven chen
2025-04-17 1:09 ` [PATCH v12 0/9] ima: kexec: measure events between kexec load and execute Stefan Berger
2025-04-20 12:21 ` 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=aAIWcwzuht+GCn29@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bauermann@kolabnow.com \
--cc=chenste@linux.microsoft.com \
--cc=code@tyhicks.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=eric.snowberg@oracle.com \
--cc=kexec@lists.infradead.org \
--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=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=stefanb@linux.ibm.com \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.