linux-kernel - Re: upstream boot error: UBSAN: null-ptr-deref in corrupted

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <202012181131.A231B861@keescook>
Date:   Fri, 18 Dec 2020 11:47:12 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     syzbot <syzbot+73d662376f16e2a7336d@...kaller.appspotmail.com>,
        LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: upstream boot error: UBSAN: null-ptr-deref in corrupted

On Thu, Dec 17, 2020 at 11:38:30AM +0100, Dmitry Vyukov wrote:
> On Thu, Dec 17, 2020 at 11:14 AM syzbot
> <syzbot+73d662376f16e2a7336d@...kaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    accefff5 Merge tag 'arm-soc-omap-genpd-5.11' of git://git...
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=14567b7f500000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=1e6efc730c219bd4
> > dashboard link: https://syzkaller.appspot.com/bug?extid=73d662376f16e2a7336d
> > compiler:       clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+73d662376f16e2a7336d@...kaller.appspotmail.com
> 
> +Kees
> 
> Not sure if it's related to UBSAN or not, but we didn't used to get
> empty stack traces.
> Either way syzbot can't boot the upstream kernel anymore.

_none_ of them? :(

Are you able to see which UBSAN config is tweaking this?

-- 
Kees Cook