[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171129050606.GF24001@zzz.localdomain>
Date: Tue, 28 Nov 2017 21:06:06 -0800
From: Eric Biggers <ebiggers3@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: syzbot
<bot+73a7bec1bc0f4fc0512a246334081f8c671762a8@...kaller.appspotmail.com>,
cl@...ux.com, iamjoonsoo.kim@....com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, penberg@...nel.org, rientjes@...gle.com,
syzkaller-bugs@...glegroups.com,
"Paul E. McKenney" <paulmck@...ibm.com>,
Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: WARNING: suspicious RCU usage (3)
On Tue, Nov 28, 2017 at 01:30:26PM -0800, Andrew Morton wrote:
>
> It looks like blkcipher_walk_done() passed a bad address to kfree().
>
Indeed, it's freeing uninitialized memory because the Salsa20 algorithms are
using the blkcipher_walk API incorrectly. I've sent a patch to fix it:
"crypto: salsa20 - fix blkcipher_walk API usage"
I am not sure why the bug reports show up as "suspicious RCU usage", though.
There were also a few other syzbot reports of this same underlying bug; I marked
them as duplicates of this one.
Eric
Powered by blists - more mailing lists