From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] Keys bugfixes
Date: Tue, 20 Oct 2015 13:50:10 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1510201346560.7943@namei.org> (raw)
Please pull these key susbystem fixes for 4.3, per the message from David
Howells:
"Here are two patches, the first of which at least should go upstream
immediately:
(1) Prevent a user-triggerable crash in the keyrings destructor when a
negatively instantiated keyring is garbage collected. I have also
seen this triggered for user type keys.
(2) Prevent the user from using requesting that a keyring be created and
instantiated through an upcall. Doing so is probably safe since the
keyring type ignores the arguments to its instantiation function -
but we probably shouldn't let keyrings be created in this manner."
---
The following changes since commit 1099f86044111e9a7807f09523e42d4c9d0fb781:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2015-10-19 09:55:40 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git for-linus
David Howells (2):
KEYS: Fix crash when attempt to garbage collect an uninstantiated keyring
KEYS: Don't permit request_key() to construct a new keyring
security/keys/gc.c | 6 ++++--
security/keys/request_key.c | 3 +++
2 files changed, 7 insertions(+), 2 deletions(-)
next reply other threads:[~2015-10-20 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 2:50 James Morris [this message]
2015-10-20 7:20 ` Linus Torvalds
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.LRH.2.20.1510201346560.7943@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®