From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Todd Kjos <tkjos@google.com>,
arve@android.com, tkjos@android.com, maco@android.com,
christian@brauner.io, James Morris <jmorris@namei.org>,
Serge Hallyn <serge@hallyn.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Eric Paris <eparis@parisplace.org>,
keescook@chromium.org, jannh@google.com,
Jeffrey Vander Stoep <jeffv@google.com>,
zohar@linux.ibm.com, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, joel@joelfernandes.org,
kernel-team@android.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] binder: use cred instead of task for selinux checks
Date: Tue, 5 Oct 2021 16:05:17 +0200 [thread overview]
Message-ID: <YVxbnQsquSrG6sxF@kroah.com> (raw)
In-Reply-To: <CAHC9VhTdyc6qagfFDLFteqTpayC4G=tNy1T7mueMKeZzU8QmwQ@mail.gmail.com>
On Tue, Oct 05, 2021 at 09:53:31AM -0400, Paul Moore wrote:
> On Tue, Oct 5, 2021 at 9:31 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Fri, Oct 01, 2021 at 10:55:21AM -0700, Todd Kjos wrote:
> > > Save the struct cred associated with a binder process
> > > at initial open to avoid potential race conditions
> > > when converting to a security ID.
> > >
> > > Since binder was integrated with selinux, it has passed
> > > 'struct task_struct' associated with the binder_proc
> > > to represent the source and target of transactions.
> > > The conversion of task to SID was then done in the hook
> > > implementations. It turns out that there are race conditions
> > > which can result in an incorrect security context being used.
> > >
> > > Fix by saving the 'struct cred' during binder_open and pass
> > > it to the selinux subsystem.
> > >
> > > Fixes: 79af73079d75 ("Add security hooks to binder and implement the
> > > hooks for SELinux.")
> > > Signed-off-by: Todd Kjos <tkjos@google.com>
> > > Cc: stable@vger.kernel.org # 5.14+ (need backport for earlier stables)
> > > ---
> > > v2: updated comments as suggested by Paul Moore
> > >
> > > drivers/android/binder.c | 14 +++++----
> > > drivers/android/binder_internal.h | 4 +++
> > > include/linux/lsm_hook_defs.h | 14 ++++-----
> > > include/linux/lsm_hooks.h | 14 ++++-----
> > > include/linux/security.h | 28 +++++++++---------
> > > security/security.c | 14 ++++-----
> > > security/selinux/hooks.c | 48 +++++++++----------------------
> > > 7 files changed, 60 insertions(+), 76 deletions(-)
> >
> > Ideally I could get an ack from the security developers before taking
> > this in my tree...
>
> This should probably go in via one of the security trees, e.g. SELinux
> or LSM, rather than the binder/driver tree.
Fine with me, take it away!
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2021-10-05 14:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 17:55 [PATCH v2] binder: use cred instead of task for selinux checks Todd Kjos
2021-10-01 18:46 ` Casey Schaufler
2021-10-01 19:36 ` Jann Horn
2021-10-01 19:50 ` Jann Horn
2021-10-01 20:10 ` Casey Schaufler
2021-10-01 22:58 ` Jann Horn
2021-10-04 16:19 ` Casey Schaufler
2021-10-04 22:28 ` Jann Horn
2021-10-04 23:37 ` Casey Schaufler
2021-10-05 0:26 ` Jann Horn
2021-10-05 15:21 ` Stephen Smalley
2021-10-05 16:49 ` Todd Kjos
2021-10-05 17:12 ` Stephen Smalley
2021-10-05 22:01 ` Paul Moore
2021-10-05 16:59 ` Casey Schaufler
2021-10-06 2:27 ` Jann Horn
2021-10-06 19:49 ` Casey Schaufler
2021-10-06 1:25 ` Jann Horn
2021-10-05 13:31 ` Greg KH
2021-10-05 13:53 ` Paul Moore
2021-10-05 14:05 ` Greg KH [this message]
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=YVxbnQsquSrG6sxF@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=devel@driverdev.osuosl.org \
--cc=eparis@parisplace.org \
--cc=jannh@google.com \
--cc=jeffv@google.com \
--cc=jmorris@namei.org \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=maco@android.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tkjos@android.com \
--cc=tkjos@google.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).