All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2] general protection fault in sock_has_perm
Date: Thu, 1 Feb 2018 18:04:47 +0100	[thread overview]
Message-ID: <20180201170447.GE12838@kroah.com> (raw)
In-Reply-To: <5fb5622d-e58b-c174-3d5c-bfe55569b88e@android.com>

On Thu, Feb 01, 2018 at 08:20:13AM -0800, Mark Salyzyn wrote:
> On 02/01/2018 08:00 AM, Paul Moore wrote:
> > On Thu, Feb 1, 2018 at 10:37 AM, Mark Salyzyn <salyzyn@android.com> wrote:
> > > In the absence of commit a4298e4522d6 ("net: add SOCK_RCU_FREE socket
> > > flag") and all the associated infrastructure changes to take advantage
> > > of a RCU grace period before freeing, there is a heightened
> > > possibility that a security check is performed while an ill-timed
> > > setsockopt call races in from user space.  It then is prudent to null
> > > check sk_security, and if the case, reject the permissions.
> > > 
> > > . . .
> > > ---[ end trace 7b5aaf788fef6174 ]---
> > > 
> > > Signed-off-by: Mark Salyzyn <salyzyn@android.com>
> > > Signed-off-by: Paul Moore <paul@linuxfoundation.org>
> > No, in the previous thread I gave my ack, not my sign-off; please be
> > more careful in the future.  It may seem silly, especially in this
> > particular case, but it is an important distinction when things like
> > the DCO are concerned.
> > 
> > Anyway, here is my ack again.
> > 
> > Acked-by: Paul Moore <paul@paul-moore.com>
> > 
> Ok, both Greg KH and yours should be considered Acked-By. Been overstepping
> this boundary for _years_. AFAIK Signed-off-by is still pending from Stephen
> Smalley <sds@tycho.nsa.gov> before this can roll in.

An ack is all I need here, or I can just rely on Paul's :)
I'll edit up Paul's when I apply this.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Salyzyn <salyzyn@android.com>
Cc: Paul Moore <paul@paul-moore.com>,
	linux-kernel@vger.kernel.org,
	Paul Moore <paul@linuxfoundation.org>,
	Eric Dumazet <edumazet@google.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org,
	Eric Paris <eparis@parisplace.org>,
	"Serge E . Hallyn" <serge@hallyn.com>,
	stable <stable@vger.kernel.org>, James Morris <jmorris@namei.org>
Subject: Re: [PATCH v2] general protection fault in sock_has_perm
Date: Thu, 1 Feb 2018 18:04:47 +0100	[thread overview]
Message-ID: <20180201170447.GE12838@kroah.com> (raw)
In-Reply-To: <5fb5622d-e58b-c174-3d5c-bfe55569b88e@android.com>

On Thu, Feb 01, 2018 at 08:20:13AM -0800, Mark Salyzyn wrote:
> On 02/01/2018 08:00 AM, Paul Moore wrote:
> > On Thu, Feb 1, 2018 at 10:37 AM, Mark Salyzyn <salyzyn@android.com> wrote:
> > > In the absence of commit a4298e4522d6 ("net: add SOCK_RCU_FREE socket
> > > flag") and all the associated infrastructure changes to take advantage
> > > of a RCU grace period before freeing, there is a heightened
> > > possibility that a security check is performed while an ill-timed
> > > setsockopt call races in from user space.  It then is prudent to null
> > > check sk_security, and if the case, reject the permissions.
> > > 
> > > . . .
> > > ---[ end trace 7b5aaf788fef6174 ]---
> > > 
> > > Signed-off-by: Mark Salyzyn <salyzyn@android.com>
> > > Signed-off-by: Paul Moore <paul@linuxfoundation.org>
> > No, in the previous thread I gave my ack, not my sign-off; please be
> > more careful in the future.  It may seem silly, especially in this
> > particular case, but it is an important distinction when things like
> > the DCO are concerned.
> > 
> > Anyway, here is my ack again.
> > 
> > Acked-by: Paul Moore <paul@paul-moore.com>
> > 
> Ok, both Greg KH and yours should be considered Acked-By. Been overstepping
> this boundary for _years_. AFAIK Signed-off-by is still pending from Stephen
> Smalley <sds@tycho.nsa.gov> before this can roll in.

An ack is all I need here, or I can just rely on Paul's :)
I'll edit up Paul's when I apply this.

thanks,

greg k-h

  parent reply	other threads:[~2018-02-01 17:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 15:37 [PATCH v2] general protection fault in sock_has_perm Mark Salyzyn
2018-02-01 15:37 ` Mark Salyzyn
2018-02-01 16:00 ` Paul Moore
2018-02-01 16:00   ` Paul Moore
2018-02-01 16:20   ` Mark Salyzyn
2018-02-01 16:20     ` Mark Salyzyn
2018-02-01 16:50     ` Paul Moore
2018-02-01 16:50       ` Paul Moore
2018-02-01 17:02     ` Stephen Smalley
2018-02-01 17:02       ` Stephen Smalley
2018-02-01 17:23       ` Mark Salyzyn
2018-02-01 17:23         ` Mark Salyzyn
2018-02-01 17:04     ` Greg KH [this message]
2018-02-01 17:04       ` Greg KH
2018-02-02 10:27 ` Greg KH
2018-02-02 10:27   ` Greg KH
2018-02-02 10:35 ` Patch "selinux: general protection fault in sock_has_perm" has been added to the 3.18-stable tree gregkh
2018-02-02 10:37 ` Patch "selinux: general protection fault in sock_has_perm" has been added to the 4.4-stable tree gregkh

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=20180201170447.GE12838@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-security-module@vger.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.