mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, security@kernel.org
Subject: [GIT PULL] Fix for Integrity subsystem null pointer deref
Date: Wed, 29 Oct 2014 14:55:34 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.11.1410291450290.28213@namei.org> (raw)

These changes fix a bug in xattr handling, where the evm and ima 
inode_setxattr() functions do not check for empty xattrs being passed from 
userspace (leading to user-triggerable null pointer dereferences).

Please pull.


The following changes since commit 9f76628da20f96a179ca62b504886f99ecc29223:

  Merge branch 'for-3.18' of git://linux-nfs.org/~bfields/linux (2014-10-28 13:32:06 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git for-linus

Dmitry Kasatkin (2):
      ima: check xattr value length and type in the ima_inode_setxattr()
      evm: check xattr value length and type in evm_inode_setxattr()

James Morris (1):
      Merge branch 'for-linus' of git://git.kernel.org/.../zohar/linux-integrity into for-linus

 security/integrity/evm/evm_main.c     |    9 ++++++---
 security/integrity/ima/ima_appraise.c |    2 ++
 security/integrity/integrity.h        |    1 +
 3 files changed, 9 insertions(+), 3 deletions(-)

             reply	other threads:[~2014-10-29  3:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  3:55 James Morris [this message]
2014-10-29  5:08 ` Andy Lutomirski
2014-10-29 12:59   ` Mimi Zohar
2014-10-29 16:23     ` Andy Lutomirski
2014-10-29 18:29       ` Mimi Zohar
2014-10-29 18:36       ` Dan Carpenter
2014-10-29 18:51         ` Andy Lutomirski
2014-10-29 20:20           ` Mimi Zohar
2014-10-29 21:22             ` Andy Lutomirski
2014-10-29 22:23               ` Dmitry Kasatkin
2014-10-29 22:24                 ` Andy Lutomirski
2014-11-08 11:25         ` Dan Carpenter

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.11.1410291450290.28213@namei.org \
    --to=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=security@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®