All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Hunt <johunt@akamai.com>
To: Ben Hutchings <ben@decadent.org.uk>, Jan Kara <jack@suse.cz>
Cc: "Levin, Alexander" <alexander.levin@verizon.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Fix for CVE-2016-7097 missing from linux-4.1.y
Date: Wed, 16 Nov 2016 11:56:52 -0600	[thread overview]
Message-ID: <582C9DE4.5020608@akamai.com> (raw)
In-Reply-To: <1478919793.2622.19.camel@decadent.org.uk>

On 11/11/2016 09:03 PM, Ben Hutchings wrote:
> On Fri, 2016-11-11 at 10:58 +0100, Jan Kara wrote:
>> Hi!
>>
>> On Thu 10-11-16 16:59:17, Josh Hunt wrote:
>>> You are the author of commit 073931017b49 ("posix_acl: Clear SGID bit when
>>> setting file permissions") which has been identified to resolve
>>> CVE-2016-7097, but is missing from linux-4.1.y.
>>>
>>> If you believe this commit should be part of linux-4.1.y can you please
>>> reply with your approval for its inclusion?
>>
>> Yes, the problem exists all the way back, I belive since ACLs were
>> introduced. Definitely exists in 3.0 which is the oldest version I've
>> checked. The patch may need some massaging to apply which is why it didn't
>> get into 4.1 I assume. And the backport will need a review because all
>> filesystems supporting ACLs need to be handled where frankly I'm not quite
>> sure the bug-severity / effort is worth it.
>
> I've attempted backports to 3.2 and 3.16, and will send those out for
> review in the next few days.
>
> Ben.

Jan/Ben

Thanks for following up on this.

Ben - I'll be on the lookout for those backports.

Thanks!
Josh

  reply	other threads:[~2016-11-16 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 22:59 Fix for CVE-2016-7097 missing from linux-4.1.y Josh Hunt
2016-11-11  9:58 ` Jan Kara
2016-11-12  3:03   ` Ben Hutchings
2016-11-16 17:56     ` Josh Hunt [this message]
2016-11-16 18:00       ` 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=582C9DE4.5020608@akamai.com \
    --to=johunt@akamai.com \
    --cc=alexander.levin@verizon.com \
    --cc=ben@decadent.org.uk \
    --cc=jack@suse.cz \
    --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 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.