public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Salyzyn <salyzyn@android.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: CVE-2016-7097 causes acl leak
Date: Sun, 11 Dec 2016 19:48:25 +0100	[thread overview]
Message-ID: <20161211184825.GA5232@kroah.com> (raw)
In-Reply-To: <bb7177d2-08dc-d75c-9012-26e3b2888461@android.com>

On Mon, Dec 05, 2016 at 09:16:31AM -0800, Mark Salyzyn wrote:
> Commit 073931017b49d9458aa351605b43a7e34598caef has several occurrences of
> an acl leak.
> 
> posix_acl_update_mode(inose, &mode, &acl);
> 
> . . .
> 
> posix_acl_release(acl);
> 
> 
> acl is NULLed in posix_acl_update_mode to signal caller to not update the
> acl; but because it is nulled, it is never released.

Any reason you didn't cc: the authors of that patch and the correct
mailing list for it (hint, use scripts/get_maintainer.pl on the
patch...)

Try that and see what happens...

thanks,

greg k-h

  reply	other threads:[~2016-12-11 20:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 17:16 CVE-2016-7097 causes acl leak Mark Salyzyn
2016-12-11 18:48 ` Greg KH [this message]
2016-12-12  0:34 ` Cong Wang
2016-12-12 10:46   ` Jan Kara
2016-12-12 21:10     ` Cong Wang
2016-12-13  0:26   ` Mark Salyzyn
2016-12-13  6:26     ` Cong Wang
2016-12-13 11:28       ` Jan Kara
2016-12-13 23:56         ` Cong Wang
2016-12-13 15:55       ` Mark Salyzyn
2016-12-13 16:07         ` Jan Kara
2016-12-13 23:42       ` Mark Salyzyn
2016-12-14  0:00         ` Greg KH
2016-12-14 20:20           ` Mark Salyzyn
2016-12-14 23:30             ` Greg KH
2016-12-15 15:22               ` Mark Salyzyn
2016-12-15 16:32                 ` Jan Kara
2016-12-13 11:17     ` Jan Kara

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=20161211184825.GA5232@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=salyzyn@android.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