From: Paul Moore <paul@paul-moore.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
casey@schaufler-ca.com, eparis@redhat.com,
linux-security-module@vger.kernel.org, audit@vger.kernel.org
Cc: jmorris@namei.org, serge@hallyn.com, keescook@chromium.org,
john.johansen@canonical.com, penguin-kernel@i-love.sakura.ne.jp,
stephen.smalley.work@gmail.com, linux-kernel@vger.kernel.org,
selinux@vger.kernel.org
Subject: Re: [PATCH v4 4/4] Audit: Add record for multiple object contexts
Date: Mon, 16 Jun 2025 16:54:52 -0400 [thread overview]
Message-ID: <88f740c7efa914435e2223e90666c8b2@paul-moore.com> (raw)
In-Reply-To: <20250607005134.10488-5-casey@schaufler-ca.com>
On Jun 6, 2025 Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> Create a new audit record AUDIT_MAC_OBJ_CONTEXTS.
> An example of the MAC_OBJ_CONTEXTS record is:
>
> type=MAC_OBJ_CONTEXTS
> msg=audit(1601152467.009:1050):
> obj_selinux=unconfined_u:object_r:user_home_t:s0
>
> When an audit event includes a AUDIT_MAC_OBJ_CONTEXTS record
> the "obj=" field in other records in the event will be "obj=?".
> An AUDIT_MAC_OBJ_CONTEXTS record is supplied when the system has
> multiple security modules that may make access decisions based
> on an object security context.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> ---
> include/linux/audit.h | 7 +++++
> include/uapi/linux/audit.h | 1 +
> kernel/audit.c | 58 +++++++++++++++++++++++++++++++++++++-
> kernel/auditsc.c | 45 ++++++++---------------------
> security/selinux/hooks.c | 3 +-
> security/smack/smack_lsm.c | 3 +-
> 6 files changed, 80 insertions(+), 37 deletions(-)
...
> diff --git a/kernel/audit.c b/kernel/audit.c
> index 0987b2f391cc..451c36965889 100644
> --- a/kernel/audit.c
> +++ b/kernel/audit.c
> @@ -2337,6 +2344,55 @@ int audit_log_task_context(struct audit_buffer *ab)
> }
> EXPORT_SYMBOL(audit_log_task_context);
>
> +int audit_log_obj_ctx(struct audit_buffer *ab, struct lsm_prop *prop)
> +{
> + int i;
> + int rc;
> + int error = 0;
> + char *space = "";
> + struct lsm_context ctx;
> +
> + if (audit_obj_secctx_cnt < 2) {
> + error = security_lsmprop_to_secctx(prop, &ctx, LSM_ID_UNDEF);
> + if (error < 0) {
> + if (error != -EINVAL)
> + goto error_path;
> + return error;
> + }
> + audit_log_format(ab, " obj=%s", ctx.context);
> + security_release_secctx(&ctx);
> + return 0;
> + }
> + audit_log_format(ab, " obj=?");
> + error = audit_buffer_aux_new(ab, AUDIT_MAC_OBJ_CONTEXTS);
> + if (error)
> + goto error_path;
> +
> + for (i = 0; i < audit_obj_secctx_cnt; i++) {
> + rc = security_lsmprop_to_secctx(prop, &ctx,
> + audit_obj_lsms[i]->id);
> + if (rc < 0) {
> + audit_log_format(ab, "%sobj_%s=?", space,
> + audit_obj_lsms[i]->name);
> + if (rc != -EINVAL)
> + audit_panic("error in audit_log_obj_ctx");
> + error = rc;
Do we need the same logic as in audit_log_subj_ctx()?
> + } else {
> + audit_log_format(ab, "%sobj_%s=%s", space,
> + audit_obj_lsms[i]->name, ctx.context);
> + security_release_secctx(&ctx);
> + }
> + space = " ";
> + }
> +
> + audit_buffer_aux_end(ab);
> + return error;
> +
> +error_path:
> + audit_panic("error in audit_log_obj_ctx");
> + return error;
> +}
> +
> void audit_log_d_path_exe(struct audit_buffer *ab,
> struct mm_struct *mm)
> {
> diff --git a/kernel/auditsc.c b/kernel/auditsc.c
> index 322d4e27f28e..0c28fa33d099 100644
> --- a/kernel/auditsc.c
> +++ b/kernel/auditsc.c
> @@ -1098,7 +1098,6 @@ static int audit_log_pid_context(struct audit_context *context, pid_t pid,
> char *comm)
> {
> struct audit_buffer *ab;
> - struct lsm_context ctx;
> int rc = 0;
>
> ab = audit_log_start(context, GFP_KERNEL, AUDIT_OBJ_PID);
> @@ -1108,15 +1107,9 @@ static int audit_log_pid_context(struct audit_context *context, pid_t pid,
> audit_log_format(ab, "opid=%d oauid=%d ouid=%d oses=%d", pid,
> from_kuid(&init_user_ns, auid),
> from_kuid(&init_user_ns, uid), sessionid);
> - if (lsmprop_is_set(prop)) {
> - if (security_lsmprop_to_secctx(prop, &ctx, LSM_ID_UNDEF) < 0) {
> - audit_log_format(ab, " obj=(none)");
> - rc = 1;
> - } else {
> - audit_log_format(ab, " obj=%s", ctx.context);
> - security_release_secctx(&ctx);
> - }
> - }
> + if (lsmprop_is_set(prop) && audit_log_obj_ctx(ab, prop))
> + rc = 1;
We should probably use the return value from audit_log_obj_ctx().
> audit_log_format(ab, " ocomm=");
> audit_log_untrustedstring(ab, comm);
> audit_log_end(ab);
...
> @@ -1780,15 +1756,16 @@ static void audit_log_exit(void)
> axs->target_sessionid[i],
> &axs->target_ref[i],
> axs->target_comm[i]))
> - call_panic = 1;
> + call_panic = 1;
> }
>
> if (context->target_pid &&
> audit_log_pid_context(context, context->target_pid,
> context->target_auid, context->target_uid,
> context->target_sessionid,
> - &context->target_ref, context->target_comm))
> - call_panic = 1;
> + &context->target_ref,
> + context->target_comm))
> + call_panic = 1;
I appreciate the indent fixes, would you mind pulling this out and
submitting them separately?
--
paul-moore.com
next prev parent reply other threads:[~2025-06-16 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250607005134.10488-1-casey.ref@schaufler-ca.com>
2025-06-07 0:51 ` [PATCH v4 0/4] Audit: Records for multiple security contexts Casey Schaufler
2025-06-07 0:51 ` [PATCH v4 1/4] Audit: Create audit_stamp structure Casey Schaufler
2025-06-07 0:51 ` [PATCH v4 2/4] LSM: security_lsmblob_to_secctx module selection Casey Schaufler
2025-06-16 20:54 ` Paul Moore
2025-06-07 0:51 ` [PATCH v4 3/4] Audit: Add record for multiple task security contexts Casey Schaufler
2025-06-16 20:54 ` Paul Moore
2025-06-07 0:51 ` [PATCH v4 4/4] Audit: Add record for multiple object contexts Casey Schaufler
2025-06-16 20:54 ` Paul Moore [this message]
2025-07-04 20:18 ` Casey Schaufler
2025-07-15 20:40 ` Casey Schaufler
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=88f740c7efa914435e2223e90666c8b2@paul-moore.com \
--to=paul@paul-moore.com \
--cc=audit@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.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