stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "vfs: Ignore unlocked mounts in fs_fully_visible" has been added to the 3.14-stable tree
Date: Wed, 8 Jul 2015 07:21:30 -0700	[thread overview]
Message-ID: <20150708142130.GA10625@kroah.com> (raw)
In-Reply-To: <874mlebwsj.fsf@x220.int.ebiederm.org>

On Wed, Jul 08, 2015 at 08:31:40AM -0500, Eric W. Biederman wrote:
> 
> Are:
> 
> mnt: Refactor the logic for mounting sysfs and proc in a user namespace 1b852bceb0d111e510d1a15826ecc4a19358d512
> mnt: Modify fs_fully_visible to deal with locked ro nodev and atime     8c6cf9cc829fcd0b179b59f7fe288941d0e31108
> 
> coming?
> 
> Anyone being able to remove the read-only mount status of
> proc and sysfs is scary bug.  I think I have seen CVE flying

I was going to wait for the next round of stable kernels for these
fixes, I had to draw the line somewhere.  I wasn't aware there was a CVE
for this, if you think they should go in now, I'll go add them.

But wasn't there more than just these two?  I see a number of patches in
my queue around this area that you were asking to be included in stable
kernels.

thanks,

greg k-h

  reply	other threads:[~2015-07-08 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08  7:22 Patch "vfs: Ignore unlocked mounts in fs_fully_visible" has been added to the 3.14-stable tree gregkh
2015-07-08 13:31 ` Eric W. Biederman
2015-07-08 14:21   ` Greg KH [this message]
2015-07-08 14:35     ` Eric W. Biederman
2015-07-08 22:07       ` Greg KH
2015-07-09  6:12         ` Greg KH
2015-07-10  6:06           ` Eric W. Biederman
2015-12-12  2:40             ` Ben Hutchings

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=20150708142130.GA10625@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ebiederm@xmission.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@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 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).