[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4564679.HlOejCIXXz@positron.chronox.de>
Date: Sun, 08 Apr 2018 17:31:46 +0200
From: Stephan Müller <smueller@...onox.de>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Matthew Wilcox <willy@...radead.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
David Miller <davem@...emloft.net>,
linux-crypto@...r.kernel.org, Eric Biggers <ebiggers3@...il.com>,
syzbot <syzbot+75397ee3df5c70164154@...kaller.appspotmail.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
syzkaller-bugs@...glegroups.com, Al Viro <viro@...iv.linux.org.uk>
Subject: Re: WARNING in kmem_cache_free
Am Sonntag, 8. April 2018, 13:18:06 CEST schrieb Dmitry Vyukov:
Hi Dmitry,
>
> Running syz-repro utility on this log, I think I've found the guilty guy:
> https://gist.githubusercontent.com/dvyukov/1dd75d55efd238e7207af1cc38478b3a/
> raw/403859b56b161a6fbb158e8953fac5bb6e73b1a1/gistfile1.txt
>
I am unable to reproduce it with the code. I am using the current
cryptodev-2.6 tree with kazan enabled. Could you please give me your kernel
config or a pointer of the used tree?
> It crashes as:
> BUG: KASAN: use-after-free in drbg_kcapi_seed+0x1178/0x12e0
> and:
> BUG: unable to handle kernel paging request at ffffebe000000020
> and with other indications of badly corrupted heap.
>
> This points to crypto/drbg.c, so +crypto maintainers.
Ciao
Stephan
Powered by blists - more mailing lists