linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Mimi Zohar" <zohar@linux.ibm.com>,
	"Luis Chamberlain" <mcgrof@kernel.org>
Cc: <linux-modules@vger.kernel.org>,
	<linux-integrity@vger.kernel.org>,
	"Roberto Sassu" <roberto.sassu@huawei.com>,
	<linux-kernel@vger.kernel.org>,
	"Ken Goldman" <kgold@linux.ibm.com>
Subject: Re: [PATCH] ima: define an init_module critical data record
Date: Wed, 27 Mar 2024 18:54:16 +0200	[thread overview]
Message-ID: <D04OU424128P.22TP02GW2CJCT@kernel.org> (raw)
In-Reply-To: <20240327150019.81477-1-zohar@linux.ibm.com>

On Wed Mar 27, 2024 at 5:00 PM EET, Mimi Zohar wrote:
> The init_module syscall loads an ELF image into kernel space without
> measuring the buffer containing the ELF image.  To close this kernel
> module integrity gap, define a new critical-data record which includes
> the hash of the ELF image.
>
> Instead of including the buffer data in the IMA measurement list,
> include the hash of the buffer data to avoid large IMA measurement
> list records.  The buffer data hash would be the same value as the
> finit_module syscall file hash.
>
> To enable measuring the init_module buffer and other critical data from
> boot, define "ima_policy=critical_data" on the boot command line.  Since
> builtin policies are not persistent, a custom IMA policy must include
> the rule as well: measure func=CRITICAL_DATA label=modules
>
> To verify the template data hash value, first convert the buffer data
> hash to binary:
> grep "init_module" \
> 	/sys/kernel/security/integrity/ima/ascii_runtime_measurements | \
> 	tail -1 | cut -d' ' -f 6 | xxd -r -p | sha256sum
>
> Reported-by: Ken Goldman <kgold@linux.ibm.com>
> Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> ---
>  security/integrity/ima/ima_main.c | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/security/integrity/ima/ima_main.c b/security/integrity/ima/ima_main.c
> index c84e8c55333d..4b4348d681a6 100644
> --- a/security/integrity/ima/ima_main.c
> +++ b/security/integrity/ima/ima_main.c
> @@ -902,6 +902,13 @@ static int ima_post_load_data(char *buf, loff_t size,
>  		return 0;
>  	}
>  
> +	/*
> +	 * Measure the init_module syscall buffer containing the ELF image.
> +	 */
> +	if (load_id == LOADING_MODULE)
> +		ima_measure_critical_data("modules", "init_module",
> +					  buf, size, true, NULL, 0);

No reason not to ack but could be just as well (passing checkpatch):

	if (load_id == LOADING_MODULE)
		ima_measure_critical_data("modules", "init_module", buf, size, true, NULL, 0);

< 100 characters

> +
>  	return 0;
>  }
>  

Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>

BR, Jarkko

  reply	other threads:[~2024-03-27 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 15:00 [PATCH] ima: define an init_module critical data record Mimi Zohar
2024-03-27 16:54 ` Jarkko Sakkinen [this message]
2024-03-27 21:37   ` Mimi Zohar
2024-03-28  3:08     ` Jarkko Sakkinen

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=D04OU424128P.22TP02GW2CJCT@kernel.org \
    --to=jarkko@kernel.org \
    --cc=kgold@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=roberto.sassu@huawei.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).