From: James Morris <james.l.morris@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 2/2] syscalls/request_key04: new test for request_key() permission check bug
Date: Wed, 10 Jan 2018 11:56:36 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1801101156230.25885@localhost> (raw)
In-Reply-To: <20180109220846.211823-2-ebiggers3@gmail.com>
On Tue, 9 Jan 2018, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Add a test for a bug that allowed the request_key() system call to be
> used to add a key to a keyring using only Search permission. This bug
> was assigned CVE-2017-17807.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: James Morris <james.l.morris@oracle.com>
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2018-01-10 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 22:08 [LTP] [PATCH v2 1/2] lapi/keyctl.h: add key permission constants Eric Biggers
2018-01-09 22:08 ` [LTP] [PATCH v2 2/2] syscalls/request_key04: new test for request_key() permission check bug Eric Biggers
2018-01-10 0:56 ` James Morris [this message]
2018-01-10 9:42 ` Richard Palethorpe
2018-01-10 11:12 ` Petr Vorel
2018-01-19 15:22 ` Cyril Hrubis
2018-01-10 0:56 ` [LTP] [PATCH v2 1/2] lapi/keyctl.h: add key permission constants James Morris
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=alpine.LFD.2.20.1801101156230.25885@localhost \
--to=james.l.morris@oracle.com \
--cc=ltp@lists.linux.it \
/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