From: Jasjiv Singh <jasjivsingh@linux.microsoft.com>
To: wufan@kernel.org, paul@paul-moore.com, jmorris@namei.org,
serge@hallyn.com, mic@digikod.net
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
jasjivsingh_microsoft <jasjivsingh@linux.microsoft.com>
Subject: [RFC PATCH v1 1/1] ipe: add script enforcement with BPRM check
Date: Tue, 29 Apr 2025 14:22:50 -0700 [thread overview]
Message-ID: <1745961770-7188-2-git-send-email-jasjivsingh@linux.microsoft.com> (raw)
In-Reply-To: <1745961770-7188-1-git-send-email-jasjivsingh@linux.microsoft.com>
From: jasjivsingh_microsoft <jasjivsingh@linux.microsoft.com>
Like direct file execution (e.g. ./script.sh), indirect file execution
(e.g. sh script.sh) needs to be enforce by IPE based on the rules.
Added a new security_bprm_creds_for_exec() hook to verify the indirect
file's integrity.
Signed-off-by: Jasjiv Singh <jasjivsingh@linux.microsoft.com>
---
security/ipe/hooks.c | 23 +++++++++++++++++++++++
security/ipe/hooks.h | 2 ++
security/ipe/ipe.c | 1 +
3 files changed, 26 insertions(+)
diff --git a/security/ipe/hooks.c b/security/ipe/hooks.c
index d0323b81cd8f..12713a0495cf 100644
--- a/security/ipe/hooks.c
+++ b/security/ipe/hooks.c
@@ -35,6 +35,29 @@ int ipe_bprm_check_security(struct linux_binprm *bprm)
return ipe_evaluate_event(&ctx);
}
+/**
+ * ipe_bprm_creds_for_exec() - ipe security hook function for bprm creds check.
+ * @bprm: Supplies a pointer to a linux_binprm structure to source the file
+ * being evaluated.
+ *
+ * This LSM hook is called when a script is checked for execution through the
+ * execveat syscall with the AT_EXECVE_CHECK flag.
+ *
+ * Return:
+ * * %0 - Success
+ * * %-EACCES - Did not pass IPE policy
+ */
+int ipe_bprm_creds_for_exec(struct linux_binprm *bprm)
+{
+ struct ipe_eval_ctx ctx = IPE_EVAL_CTX_INIT;
+
+ if (!bprm->is_check)
+ return 0;
+
+ ipe_build_eval_ctx(&ctx, bprm->file, IPE_OP_EXEC, IPE_HOOK_BPRM_CHECK);
+ return ipe_evaluate_event(&ctx);
+}
+
/**
* ipe_mmap_file() - ipe security hook function for mmap check.
* @f: File being mmap'd. Can be NULL in the case of anonymous memory.
diff --git a/security/ipe/hooks.h b/security/ipe/hooks.h
index 38d4a387d039..1c16a25d806e 100644
--- a/security/ipe/hooks.h
+++ b/security/ipe/hooks.h
@@ -24,6 +24,8 @@ enum ipe_hook_type {
int ipe_bprm_check_security(struct linux_binprm *bprm);
+int ipe_bprm_creds_for_exec(struct linux_binprm *bprm);
+
int ipe_mmap_file(struct file *f, unsigned long reqprot, unsigned long prot,
unsigned long flags);
diff --git a/security/ipe/ipe.c b/security/ipe/ipe.c
index 4317134cb0da..845e3fd7a345 100644
--- a/security/ipe/ipe.c
+++ b/security/ipe/ipe.c
@@ -47,6 +47,7 @@ struct ipe_inode *ipe_inode(const struct inode *inode)
static struct security_hook_list ipe_hooks[] __ro_after_init = {
LSM_HOOK_INIT(bprm_check_security, ipe_bprm_check_security),
+ LSM_HOOK_INIT(bprm_creds_for_exec, ipe_bprm_creds_for_exec),
LSM_HOOK_INIT(mmap_file, ipe_mmap_file),
LSM_HOOK_INIT(file_mprotect, ipe_file_mprotect),
LSM_HOOK_INIT(kernel_read_file, ipe_kernel_read_file),
--
2.34.1
next prev parent reply other threads:[~2025-04-29 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 21:22 [RFC PATCH v1 0/1] ipe: added " Jasjiv Singh
2025-04-29 21:22 ` Jasjiv Singh [this message]
2025-04-30 23:29 ` [RFC PATCH v1 1/1] ipe: add " Fan Wu
2025-04-30 23:24 ` [RFC PATCH v1 0/1] ipe: added " Fan Wu
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=1745961770-7188-2-git-send-email-jasjivsingh@linux.microsoft.com \
--to=jasjivsingh@linux.microsoft.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=wufan@kernel.org \
/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
all inboxes | Powered by JetHome®