From: Greg KH <gregkh@linuxfoundation.org>
To: David Howells <dhowells@redhat.com>
Cc: jmorris@namei.org, Don Zickus <dzickus@redhat.com>,
Prarit Bhargava <prarit@redhat.com>,
Yevgeny Pats <yevgeny@perception-point.io>,
linux-kernel@vger.kernel.org, Jarod Wilson <jarod@redhat.com>,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH] KEYS: Fix keyring ref leak in join_session_keyring()
Date: Wed, 20 Jan 2016 00:20:39 -0800 [thread overview]
Message-ID: <20160120082039.GA22945@kroah.com> (raw)
In-Reply-To: <20160119220904.3102.51075.stgit@warthog.procyon.org.uk>
On Tue, Jan 19, 2016 at 10:09:04PM +0000, David Howells wrote:
> From: Yevgeny Pats <yevgeny@perception-point.io>
>
> This fixes CVE-2016-0728.
>
> If a thread is asked to join as a session keyring the keyring that's already
> set as its session, we leak a keyring reference.
>
> This can be tested with the following program:
>
> #include <stddef.h>
> #include <stdio.h>
> #include <sys/types.h>
> #include <keyutils.h>
>
> int main(int argc, const char *argv[])
> {
> int i = 0;
> key_serial_t serial;
>
> serial = keyctl(KEYCTL_JOIN_SESSION_KEYRING,
> "leaked-keyring");
> if (serial < 0) {
> perror("keyctl");
> return -1;
> }
>
> if (keyctl(KEYCTL_SETPERM, serial,
> KEY_POS_ALL | KEY_USR_ALL) < 0) {
> perror("keyctl");
> return -1;
> }
>
> for (i = 0; i < 100; i++) {
> serial = keyctl(KEYCTL_JOIN_SESSION_KEYRING,
> "leaked-keyring");
> if (serial < 0) {
> perror("keyctl");
> return -1;
> }
> }
>
> return 0;
> }
>
> If, after the program has run, there something like the following line in
> /proc/keys:
>
> 3f3d898f I--Q--- 100 perm 3f3f0000 0 0 keyring leaked-keyring: empty
>
> with a usage count of 100 * the number of times the program has been run,
> then the kernel is malfunctioning. If leaked-keyring has zero usages or
> has been garbage collected, then the problem is fixed.
>
> Reported-by: Yevgeny Pats <yevgeny@perception-point.io>
> Signed-off-by: David Howells <dhowells@redhat.com>
> Acked-by: Don Zickus <dzickus@redhat.com>
> Acked-by: Prarit Bhargava <prarit@redhat.com>
> Acked-by: Jarod Wilson <jarod@redhat.com>
Any reason you didn't tag this for stable kernels?
thanks,
greg k-h
next prev parent reply other threads:[~2016-01-20 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 22:09 David Howells
2016-01-20 8:20 ` Greg KH [this message]
2016-01-20 9:36 ` David Howells
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=20160120082039.GA22945@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dhowells@redhat.com \
--cc=dzickus@redhat.com \
--cc=jarod@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=yevgeny@perception-point.io \
/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
Powered by JetHome