From: Ondrej Mosnacek <omosnace@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: selinux@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>,
Casey Schaufler <casey@schaufler-ca.com>,
Tejun Heo <tj@kernel.org>,
lkp@01.org, kernel test robot <rong.a.chen@intel.com>
Subject: Re: [PATCH v2] kernfs: fix xattr name handling in LSM helpers
Date: Mon, 1 Apr 2019 11:47:07 +0200 [thread overview]
Message-ID: <CAFqZXNud0Q4ANgkGBjnzxJfbZ2+hP5iHyT8BGuvL8EaM7AQDxw@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhQsi-gf2BQOcNLzF=JDZ=0Noj3DQH3iA+7FC3ThwN4BAg@mail.gmail.com>
On Fri, Mar 29, 2019 at 2:31 PM Paul Moore <paul@paul-moore.com> wrote:
> On Tue, Mar 26, 2019 at 8:12 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > The implementation of kernfs_security_xattr_*() helpers reuses the
> > kernfs_node_xattr_*() functions, which take the suffix of the xattr name
> > and extract full xattr name from it using xattr_full_name(). However,
> > this function relies on the fact that the suffix passed to xattr
> > handlers from VFS is always constructed from the full name by just
> > incerementing the pointer. This doesn't necessarily hold for the callers
> > of kernfs_security_xattr_*(), so their usage will easily lead to
> > out-of-bounds access.
> >
> > Fix this by converting the helpers to take the full xattr name instead
> > of just the suffix and moving the reconstruction to the xattr handlers.
> > We now need to check if the prefix is correct in the helpers, but it
> > saves us the difficulty of reconstructing the full name from just the
> > plain suffix.
> >
> > Reported-by: kernel test robot <rong.a.chen@intel.com>
> > Fixes: b230d5aba2d1 ("LSM: add new hook for kernfs node initialization")
> > Fixes: ec882da5cda9 ("selinux: implement the kernfs_init_security hook")
> > Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
> > ---
> >
> > v2: Rebase on current selinux/next.
> >
> > fs/kernfs/inode.c | 38 ++++++++++++++++++--------------------
> > include/linux/kernfs.h | 8 ++++----
> > security/selinux/hooks.c | 6 +++---
> > 3 files changed, 25 insertions(+), 27 deletions(-)
>
> Thanks for diagnosing this and providing a patch. I haven't seen any
> objections, but I do have some questions (below).
>
> > diff --git a/fs/kernfs/inode.c b/fs/kernfs/inode.c
> > index 673ef598d97d..1daa8aa9ec96 100644
> > --- a/fs/kernfs/inode.c
> > +++ b/fs/kernfs/inode.c
> > @@ -288,28 +288,20 @@ int kernfs_iop_permission(struct inode *inode, int mask)
> > return generic_permission(inode, mask);
> > }
> >
> > -static int kernfs_node_xattr_get(const struct xattr_handler *handler,
> > - struct kernfs_node *kn, const char *suffix,
> > +static int kernfs_node_xattr_get(struct kernfs_node *kn, const char *name,
> > void *value, size_t size)
> > {
> > - const char *name = xattr_full_name(handler, suffix);
> > - struct kernfs_iattrs *attrs;
> > -
> > - attrs = kernfs_iattrs_noalloc(kn);
> > + struct kernfs_iattrs *attrs = kernfs_iattrs_noalloc(kn);
> > if (!attrs)
> > return -ENODATA;
> >
> > return simple_xattr_get(&attrs->xattrs, name, value, size);
> > }
> >
> > -static int kernfs_node_xattr_set(const struct xattr_handler *handler,
> > - struct kernfs_node *kn, const char *suffix,
> > +static int kernfs_node_xattr_set(struct kernfs_node *kn, const char *name,
> > const void *value, size_t size, int flags)
> > {
> > - const char *name = xattr_full_name(handler, suffix);
> > - struct kernfs_iattrs *attrs;
> > -
> > - attrs = kernfs_iattrs(kn);
> > + struct kernfs_iattrs *attrs = kernfs_iattrs(kn);
> > if (!attrs)
> > return -ENOMEM;
> >
>
> ...
>
> > -int kernfs_security_xattr_get(struct kernfs_node *kn, const char *suffix,
> > +int kernfs_security_xattr_get(struct kernfs_node *kn, const char *name,
> > void *value, size_t size)
> > {
> > - return kernfs_node_xattr_get(&kernfs_security_xattr_handler,
> > - kn, suffix, value, size);
> > + if (WARN_ON_ONCE(!strstarts(name, XATTR_SECURITY_PREFIX)))
> > + return -EINVAL;
> > +
> > + return kernfs_node_xattr_get(kn, name, value, size);
> > }
> >
> > -int kernfs_security_xattr_set(struct kernfs_node *kn, const char *suffix,
> > +int kernfs_security_xattr_set(struct kernfs_node *kn, const char *name,
> > void *value, size_t size, int flags)
> > {
> > - return kernfs_node_xattr_set(&kernfs_security_xattr_handler,
> > - kn, suffix, value, size, flags);
> > + if (WARN_ON_ONCE(!strstarts(name, XATTR_SECURITY_PREFIX)))
> > + return -EINVAL;
> > +
> > + return kernfs_node_xattr_set(kn, name, value, size, flags);
> > }
>
> I think it is reasonable to ask if we even need
> kernfs_security_xattr_{set|get}()? Can we just call the respective
> kernfs_node_xattr*() functions instead? I can't imagine the
> WARN_ON_ONCE check being that important.
Indeed, it is now much more natural to just expose all xattrs in those
helpers... I concur that the encapsulation doesn't seem to be worth it
any more. Let me do a simplified respin...
--
Ondrej Mosnacek <omosnace at redhat dot com>
Software Engineer, Security Technologies
Red Hat, Inc.
WARNING: multiple messages have this Message-ID (diff)
From: Ondrej Mosnacek <omosnace@redhat.com>
To: lkp@lists.01.org
Subject: Re: [PATCH v2] kernfs: fix xattr name handling in LSM helpers
Date: Mon, 01 Apr 2019 11:47:07 +0200 [thread overview]
Message-ID: <CAFqZXNud0Q4ANgkGBjnzxJfbZ2+hP5iHyT8BGuvL8EaM7AQDxw@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhQsi-gf2BQOcNLzF=JDZ=0Noj3DQH3iA+7FC3ThwN4BAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5023 bytes --]
On Fri, Mar 29, 2019 at 2:31 PM Paul Moore <paul@paul-moore.com> wrote:
> On Tue, Mar 26, 2019 at 8:12 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > The implementation of kernfs_security_xattr_*() helpers reuses the
> > kernfs_node_xattr_*() functions, which take the suffix of the xattr name
> > and extract full xattr name from it using xattr_full_name(). However,
> > this function relies on the fact that the suffix passed to xattr
> > handlers from VFS is always constructed from the full name by just
> > incerementing the pointer. This doesn't necessarily hold for the callers
> > of kernfs_security_xattr_*(), so their usage will easily lead to
> > out-of-bounds access.
> >
> > Fix this by converting the helpers to take the full xattr name instead
> > of just the suffix and moving the reconstruction to the xattr handlers.
> > We now need to check if the prefix is correct in the helpers, but it
> > saves us the difficulty of reconstructing the full name from just the
> > plain suffix.
> >
> > Reported-by: kernel test robot <rong.a.chen@intel.com>
> > Fixes: b230d5aba2d1 ("LSM: add new hook for kernfs node initialization")
> > Fixes: ec882da5cda9 ("selinux: implement the kernfs_init_security hook")
> > Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
> > ---
> >
> > v2: Rebase on current selinux/next.
> >
> > fs/kernfs/inode.c | 38 ++++++++++++++++++--------------------
> > include/linux/kernfs.h | 8 ++++----
> > security/selinux/hooks.c | 6 +++---
> > 3 files changed, 25 insertions(+), 27 deletions(-)
>
> Thanks for diagnosing this and providing a patch. I haven't seen any
> objections, but I do have some questions (below).
>
> > diff --git a/fs/kernfs/inode.c b/fs/kernfs/inode.c
> > index 673ef598d97d..1daa8aa9ec96 100644
> > --- a/fs/kernfs/inode.c
> > +++ b/fs/kernfs/inode.c
> > @@ -288,28 +288,20 @@ int kernfs_iop_permission(struct inode *inode, int mask)
> > return generic_permission(inode, mask);
> > }
> >
> > -static int kernfs_node_xattr_get(const struct xattr_handler *handler,
> > - struct kernfs_node *kn, const char *suffix,
> > +static int kernfs_node_xattr_get(struct kernfs_node *kn, const char *name,
> > void *value, size_t size)
> > {
> > - const char *name = xattr_full_name(handler, suffix);
> > - struct kernfs_iattrs *attrs;
> > -
> > - attrs = kernfs_iattrs_noalloc(kn);
> > + struct kernfs_iattrs *attrs = kernfs_iattrs_noalloc(kn);
> > if (!attrs)
> > return -ENODATA;
> >
> > return simple_xattr_get(&attrs->xattrs, name, value, size);
> > }
> >
> > -static int kernfs_node_xattr_set(const struct xattr_handler *handler,
> > - struct kernfs_node *kn, const char *suffix,
> > +static int kernfs_node_xattr_set(struct kernfs_node *kn, const char *name,
> > const void *value, size_t size, int flags)
> > {
> > - const char *name = xattr_full_name(handler, suffix);
> > - struct kernfs_iattrs *attrs;
> > -
> > - attrs = kernfs_iattrs(kn);
> > + struct kernfs_iattrs *attrs = kernfs_iattrs(kn);
> > if (!attrs)
> > return -ENOMEM;
> >
>
> ...
>
> > -int kernfs_security_xattr_get(struct kernfs_node *kn, const char *suffix,
> > +int kernfs_security_xattr_get(struct kernfs_node *kn, const char *name,
> > void *value, size_t size)
> > {
> > - return kernfs_node_xattr_get(&kernfs_security_xattr_handler,
> > - kn, suffix, value, size);
> > + if (WARN_ON_ONCE(!strstarts(name, XATTR_SECURITY_PREFIX)))
> > + return -EINVAL;
> > +
> > + return kernfs_node_xattr_get(kn, name, value, size);
> > }
> >
> > -int kernfs_security_xattr_set(struct kernfs_node *kn, const char *suffix,
> > +int kernfs_security_xattr_set(struct kernfs_node *kn, const char *name,
> > void *value, size_t size, int flags)
> > {
> > - return kernfs_node_xattr_set(&kernfs_security_xattr_handler,
> > - kn, suffix, value, size, flags);
> > + if (WARN_ON_ONCE(!strstarts(name, XATTR_SECURITY_PREFIX)))
> > + return -EINVAL;
> > +
> > + return kernfs_node_xattr_set(kn, name, value, size, flags);
> > }
>
> I think it is reasonable to ask if we even need
> kernfs_security_xattr_{set|get}()? Can we just call the respective
> kernfs_node_xattr*() functions instead? I can't imagine the
> WARN_ON_ONCE check being that important.
Indeed, it is now much more natural to just expose all xattrs in those
helpers... I concur that the encapsulation doesn't seem to be worth it
any more. Let me do a simplified respin...
--
Ondrej Mosnacek <omosnace@redhat dot com>
Software Engineer, Security Technologies
Red Hat, Inc.
next prev parent reply other threads:[~2019-04-01 9:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 14:50 [kernfs] e19dfdc83b: BUG:KASAN:global-out-of-bounds_in_s kernel test robot
2019-03-25 14:50 ` kernel test robot
2019-03-25 15:16 ` Paul Moore
2019-03-25 17:06 ` Ondrej Mosnacek
2019-03-25 17:06 ` Ondrej Mosnacek
2019-03-26 12:33 ` Ondrej Mosnacek
2019-03-26 12:33 ` Ondrej Mosnacek
2019-03-26 8:17 ` [PATCH] kernfs: fix xattr name handling in LSM helpers Ondrej Mosnacek
2019-03-26 8:17 ` Ondrej Mosnacek
2019-03-26 12:12 ` [PATCH v2] " Ondrej Mosnacek
2019-03-26 12:12 ` Ondrej Mosnacek
2019-03-29 13:31 ` Paul Moore
2019-04-01 9:47 ` Ondrej Mosnacek [this message]
2019-04-01 9:47 ` Ondrej Mosnacek
2019-04-01 10:34 ` [PATCH v3] " Ondrej Mosnacek
2019-04-01 10:34 ` Ondrej Mosnacek
2019-04-02 23:10 ` Paul Moore
2019-04-03 1:23 ` Paul Moore
2019-04-03 7:25 ` Ondrej Mosnacek
2019-04-03 7:25 ` Ondrej Mosnacek
2019-04-04 13:09 ` Paul Moore
2019-04-03 7:29 ` [PATCH v4] " Ondrej Mosnacek
2019-04-03 7:29 ` Ondrej Mosnacek
2019-04-04 13:10 ` Paul Moore
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=CAFqZXNud0Q4ANgkGBjnzxJfbZ2+hP5iHyT8BGuvL8EaM7AQDxw@mail.gmail.com \
--to=omosnace@redhat.com \
--cc=casey@schaufler-ca.com \
--cc=lkp@01.org \
--cc=paul@paul-moore.com \
--cc=rong.a.chen@intel.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.