linux-kernel - Re: kernel BUG at mm/slab.c:LINE! (2)

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: <35087252-a5fa-c162-efb2-aa2b6a30515a@iogearbox.net>
Date:   Mon, 9 Jul 2018 18:30:47 +0200
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Dmitry Vyukov <dvyukov@...gle.com>,
        Christopher Lameter <cl@...ux.com>,
        Alexei Starovoitov <ast@...nel.org>,
        netdev <netdev@...r.kernel.org>
Cc:     syzbot <syzbot+885bda95271928dc24eb@...kaller.appspotmail.com>,
        Kees Cook <keescook@...omium.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: kernel BUG at mm/slab.c:LINE! (2)

On 07/09/2018 06:16 PM, Dmitry Vyukov wrote:
> On Mon, Jul 9, 2018 at 6:05 PM, Christopher Lameter <cl@...ux.com> wrote:
>> On Sun, 8 Jul 2018, syzbot wrote:
>>
>>> kernel BUG at mm/slab.c:4421!
>>
>> Classic location that indicates memory corruption. Can we rerun this with
>> CONFIG_SLAB_DEBUG? Alternatively use SLUB debugging for better debugging
>> without rebuilding.
> 
> This runs with KASAN which is way more powerful than slab/slub debug.
> 
> There two other recent crashes in bpf_test_finish which has more info:
> 
> https://syzkaller.appspot.com/bug?id=f831c88feddf5f4de09b846bbe53e5b8c06e5c02
> https://syzkaller.appspot.com/bug?id=059cee5623ce519359e7440ba6d0d6af8b82694e

Fyi, looking into the two today as well.