From: Greg KH <gregkh@linuxfoundation.org>
To: Todd Kjos <tkjos@google.com>
Cc: stable@vger.kernel.org, arve@android.com, tkjos@android.com,
maco@android.com, christian@brauner.io, jmorris@namei.org,
serge@hallyn.com, paul@paul-moore.com,
stephen.smalley.work@gmail.com, eparis@parisplace.org,
keescook@chromium.org, jannh@google.com, jeffv@google.com,
zohar@linux.ibm.com, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org, devel@driverdev.osuosl.org,
joel@joelfernandes.org, kernel-team@android.com,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH 4.4 2/2] binder: use cred instead of task for selinux checks
Date: Fri, 12 Nov 2021 17:14:22 +0100 [thread overview]
Message-ID: <YY6S3uN478Mk6+Y1@kroah.com> (raw)
In-Reply-To: <YY6SOlQicRp1/BZF@kroah.com>
On Fri, Nov 12, 2021 at 05:11:38PM +0100, Greg KH wrote:
> On Wed, Nov 10, 2021 at 02:59:10PM -0800, Todd Kjos wrote:
> > commit 52f88693378a58094c538662ba652aff0253c4fe upstream.
> >
> > 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 using the 'struct cred' saved during binder_open and pass
> > it to the selinux subsystem.
> >
> > Cc: stable@vger.kernel.org # 5.14 (need backport for earlier stables)
> > Fixes: 79af73079d75 ("Add security hooks to binder and implement the hooks for SELinux.")
> > Suggested-by: Jann Horn <jannh@google.com>
> > Signed-off-by: Todd Kjos <tkjos@google.com>
> > Acked-by: Casey Schaufler <casey@schaufler-ca.com>
> > Signed-off-by: Paul Moore <paul@paul-moore.com>
> > Change-Id: Id7157515d2b08f11683aeb8ad9b8f1da075d34e7
> > ---
> > drivers/android/binder.c | 18 +++++++++---------
> > include/linux/lsm_hooks.h | 32 ++++++++++++++++----------------
> > include/linux/security.h | 28 ++++++++++++++--------------
> > security/security.c | 14 +++++++-------
> > security/selinux/hooks.c | 31 +++++++++++++------------------
> > 5 files changed, 59 insertions(+), 64 deletions(-)
>
> This doesn't apply at all. I've applied patch 1/2 here, but can you
> redo this one and submit it again?
Ugh, nope, my fault, sorry, this worked just fine.
It's been a long day...
greg k-h
prev parent reply other threads:[~2021-11-12 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 22:59 [PATCH 4.4 1/2] binder: use euid from cred instead of using task Todd Kjos
2021-11-10 22:59 ` [PATCH 4.4 2/2] binder: use cred instead of task for selinux checks Todd Kjos
2021-11-12 16:11 ` Greg KH
2021-11-12 16:14 ` 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=YY6S3uN478Mk6+Y1@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=casey@schaufler-ca.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-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