linux-kernel - Re: [PATCH] Fix size argument to memset call in nfsacl

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: <alpine.LNX.2.00.1102232327010.28678@swampdragon.chaosbits.net>
Date:	Wed, 23 Feb 2011 23:27:21 +0100 (CET)
From:	Jesper Juhl <jj@...osbits.net>
To:	Trond Myklebust <Trond.Myklebust@...app.com>
cc:	Chuck Lever <chuck.lever@...cle.com>,
	Milton Miller <miltonm@....com>, linux-nfs@...r.kernel.org,
	linux-kernel@...r.kernel.org, Neil Brown <neilb@...e.de>,
	bfields@...ldses.org
Subject: Re: [PATCH] Fix size argument to memset call in nfsacl_encode

On Wed, 23 Feb 2011, Jesper Juhl wrote:

> On Thu, 3 Feb 2011, Trond Myklebust wrote:
> 
> > On Thu, 2011-02-03 at 15:29 -0500, Chuck Lever wrote: 
> > > Sorry, I wasn't clear.  IMO, data that is destined for the network is an important case where we have to be careful about the rule of using either assignments or memset(), not both, when initializing a data structure.
> > > 
> > > If the compiler doesn't pack the fields in struct posix_acl, there is unused space between them.  Memory for acl2 comes from the stack, which contains arbitrary data when this function is invoked.  The areas between the structure fields are not affected by the variable assignments used here.  If the data in acl2 is then simply memcpy'd to the XDR buffer, that old stack data can possibly appear on the wire.
> > > 
> > > I agree that the current memset() is incorrect.  My conditional ACK was more about what happens in xdr_encode_array2() rather than how the posix_acl acl2 is initialized.  I think in that regard we are also safe, if the array encoding operates by data type rather than by simply doing a blanket memcpy.  See xdr_nfsace_encode().  It's always possible I misunderstood how ACEs are XDR encoded.
> > 
> > We shouldn't ever be memcopying entire structures directly to or from
> > the XDR buffer, and as far as I know, the current code will always copy
> > them element by element.
> > 
> Ok. So, could we merge the patch that kills the memcpy() ? 
> 
I mean memset() of course. 

-- 
Jesper Juhl <jj@...osbits.net>            http://www.chaosbits.net/
Plain text mails only, please.
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html

--
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/