From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
David Howells <dhowells@redhat.com>
Subject: [GIT PULL] Keys fixes
Date: Thu, 27 Oct 2016 15:37:21 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1610271536050.26214@namei.org> (raw)
Please pull these fixes from David Howells:
(1) Fix a buffer overflow when displaying /proc/keys [CVE-2016-7042].
(2) Fix broken initialisation in the big_key implementation that can
result in an oops.
(3) Make big_key depend on having a random number generator available in
Kconfig.
---
The following changes since commit 9fe68cad6e74967b88d0c6aeca7d9cd6b6e91942:
Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 (2016-10-24 21:34:13 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git for-linus
Artem Savkov (1):
security/keys: make BIG_KEYS dependent on stdrng.
David Howells (2):
KEYS: Fix short sprintf buffer in /proc/keys show function
KEYS: Sort out big_key initialisation
security/keys/Kconfig | 2 +-
security/keys/big_key.c | 59 +++++++++++++++++++++++++---------------------
security/keys/proc.c | 2 +-
3 files changed, 34 insertions(+), 29 deletions(-)
next reply other threads:[~2016-10-27 4:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 4:37 James Morris [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-18 8:23 [GIT PULL] KEYS: Fixes David Howells
2017-10-17 22:57 David Howells
2017-10-17 23:23 ` Eric Biggers
2016-11-25 1:32 [GIT PULL] Keys fixes James Morris
2016-07-18 2:06 [GIT PULL] KEYS fixes 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.LRH.2.20.1610271536050.26214@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
Powered by JetHome