public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: Christian Brauner <brauner@kernel.org>,
	 Paul Moore <paul@paul-moore.com>
Cc: "Günther Noack" <gnoack@google.com>,
	"Jann Horn" <jannh@google.com>,
	"Kees Cook" <keescook@chromium.org>,
	"Konstantin Meskhidze" <konstantin.meskhidze@huawei.com>,
	"Serge E . Hallyn" <serge@hallyn.com>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH] landlock: Use f_cred in security_file_open() hook
Date: Thu, 7 Mar 2024 16:16:41 +0100	[thread overview]
Message-ID: <20240307.eeluu4OoJ4la@digikod.net> (raw)
In-Reply-To: <20240307-fehlten-gewinn-18c93d5fb9e6@brauner>

On Thu, Mar 07, 2024 at 11:17:13AM +0100, Christian Brauner wrote:
> On Thu, Mar 07, 2024 at 10:52:03AM +0100, Mickaël Salaün wrote:
> > Use landlock_cred(file->f_cred)->domain instead of
> > landlock_get_current_domain() in security_file_open() hook
> > implementation.
> > 
> > This should not change the current behavior but could avoid potential
> > race conditions in case of current task's credentials change.
> 
> I have no problem with the patch but I'm curious how that credential
> change could happen behind your back?

I hope nothing would change it (except maybe io_uring?), but it is
(more) atomic with the security_file_alloc() call and consistent with
Landlock's current (allowed_access) and future (f_cred) checks on files.

I chatted a bit with Paul and it resulted that is difficult to get
strong guarantees about credential consistency (i.e. following all call
sites).  Anyway, it also looks safer to follow the same approach as most
LSMs.

> 
> > 
> > This will also ensure consistency with upcoming audit support relying on
> > file->f_cred.
> > 
> > Add and use a new get_fs_domain() helper to mask non-filesystem domains.
> > 
> > file->f_cred is set by path_openat()/alloc_empty_file()/init_file() just
> > before calling security_file_alloc().
> > 
> > Cc: Christian Brauner <brauner@kernel.org>
> > Cc: Günther Noack <gnoack@google.com>
> > Cc: Jann Horn <jannh@google.com>
> > Cc: Kees Cook <keescook@chromium.org>
> > Cc: Paul Moore <paul@paul-moore.com>
> > Signed-off-by: Mickaël Salaün <mic@digikod.net>
> > Link: https://lore.kernel.org/r/20240307095203.1467189-1-mic@digikod.net
> > ---
> >  security/landlock/fs.c | 18 +++++++++++-------
> >  1 file changed, 11 insertions(+), 7 deletions(-)
> > 
> > diff --git a/security/landlock/fs.c b/security/landlock/fs.c
> > index 6f0bf1434a2c..c15559432d3d 100644
> > --- a/security/landlock/fs.c
> > +++ b/security/landlock/fs.c
> > @@ -248,15 +248,18 @@ get_handled_fs_accesses(const struct landlock_ruleset *const domain)
> >  	       LANDLOCK_ACCESS_FS_INITIALLY_DENIED;
> >  }
> >  
> > -static const struct landlock_ruleset *get_current_fs_domain(void)
> > +static const struct landlock_ruleset *
> > +get_fs_domain(const struct landlock_ruleset *const domain)
> >  {
> > -	const struct landlock_ruleset *const dom =
> > -		landlock_get_current_domain();
> > -
> > -	if (!dom || !get_raw_handled_fs_accesses(dom))
> > +	if (!domain || !get_raw_handled_fs_accesses(domain))
> >  		return NULL;
> >  
> > -	return dom;
> > +	return domain;
> > +}
> > +
> > +static const struct landlock_ruleset *get_current_fs_domain(void)
> > +{
> > +	return get_fs_domain(landlock_get_current_domain());
> >  }
> >  
> >  /*
> > @@ -1334,7 +1337,8 @@ static int hook_file_open(struct file *const file)
> >  	layer_mask_t layer_masks[LANDLOCK_NUM_ACCESS_FS] = {};
> >  	access_mask_t open_access_request, full_access_request, allowed_access;
> >  	const access_mask_t optional_access = LANDLOCK_ACCESS_FS_TRUNCATE;
> > -	const struct landlock_ruleset *const dom = get_current_fs_domain();
> > +	const struct landlock_ruleset *const dom =
> > +		get_fs_domain(landlock_cred(file->f_cred)->domain);
> >  
> >  	if (!dom)
> >  		return 0;
> > -- 
> > 2.44.0
> > 

  reply	other threads:[~2024-03-07 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  9:52 [PATCH] landlock: Use f_cred in security_file_open() hook Mickaël Salaün
2024-03-07 10:17 ` Christian Brauner
2024-03-07 15:16   ` Mickaël Salaün [this message]
2024-03-07 17:54 ` Kees Cook

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=20240307.eeluu4OoJ4la@digikod.net \
    --to=mic@digikod.net \
    --cc=brauner@kernel.org \
    --cc=gnoack@google.com \
    --cc=jannh@google.com \
    --cc=keescook@chromium.org \
    --cc=konstantin.meskhidze@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.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