linux-kernel - Re: [PATCH v3 0/3] integrity: NULL pointer dereference fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1414506184.6815.111.camel@dhcp-9-2-203-236.watson.ibm.com>
Date:	Tue, 28 Oct 2014 10:23:04 -0400
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	Dmitry Kasatkin <d.kasatkin@...sung.com>
Cc:	linux-security-module@...r.kernel.org,
	linux-ima-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, jack@...e.cz, jmorris@...ei.org,
	dmitry.kasatkin@...il.com
Subject: Re: [PATCH v3 0/3] integrity: NULL pointer dereference fixes

On Tue, 2014-10-28 at 13:31 +0200, Dmitry Kasatkin wrote: 
> Hi,
> 
> Recently Jan Kara reported about possible NULL pointer dereference
> in IMA and EVM setxattr hooks. This patchset fixes the problem.
> 
> http://sourceforge.net/p/linux-ima/mailman/message/32957578
> 
> In this version of the patchset we agreed with Mimi to split IMA
> patch into two, where the first patch fixes the oops and must go to
> the stable and the second patch limits setting of file hash to fix
> and log modes and may go to the next kernel version via normal process.

Thanks, Dmitry.  James, I'll send you a pull request shortly for Linus,
deferring one patch until the 3.19 open window.

For-Linus: 
[PATCH v3 1/3] ima: check xattr value length and type in the ima_inode_setxattr()
                                  [P
ATCH v3 1/1] evm: check xattr value
length and type in
evm_inode_setxattr()

3.19: [v3 2/3] ima: limit file hash setting by user to fix and log modes

Mimi

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/