mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, keyrings@linux-nfs.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [GIT PULL] Keyrings fixes, including one CVE fix
Date: Wed, 07 Jan 2015 16:23:56 +0000	[thread overview]
Message-ID: <31158.1420647836@warthog.procyon.org.uk> (raw)

Hi James,

Could you pass these on to Linus please?  There are two fixes:

 (1) Fix for the order in which things are done during key garbage
     collection to prevent named keyrings causing a crash [CVE-2014-9529].

 (2) Fix assoc_array to explicitly #include rcupdate.h to prevent compilation
     errors under certain circumstances.

David
---
The following changes since commit 693a30b8f19a964087a3762d09fb2e1cbad6b0d4:

  Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml (2015-01-04 11:46:43 -0800)

are available in the git repository at:


  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-fixes-20150107

for you to fetch changes up to 990428b8ead311c68a850ead7ec8557a10b8893a:

  assoc_array: Include rcupdate.h for call_rcu() definition (2015-01-07 16:08:41 +0000)

----------------------------------------------------------------
(from the branch description for keys-fixes local branch)

Keyrings fixes
Keyrings fixes

----------------------------------------------------------------
Pranith Kumar (1):
      assoc_array: Include rcupdate.h for call_rcu() definition

Sasha Levin (1):
      KEYS: close race between key lookup and freeing

 lib/assoc_array.c  | 1 +
 security/keys/gc.c | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

             reply	other threads:[~2015-01-07 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 16:23 David Howells [this message]
2015-01-07 21:07 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=31158.1420647836@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=stable@vger.kernel.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®