linux-kernel - Re: KASAN: alloca-out-of-bounds Read in unwind_next

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]

Date:   Fri, 13 Apr 2018 13:16:03 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Josh Poimboeuf <jpoimboe@...hat.com>
Cc:     syzbot <syzbot+9d1d9866b0b8ee6e0a8c@...kaller.appspotmail.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Ingo Molnar <mingo@...hat.com>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        "the arch/x86 maintainers" <x86@...nel.org>,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: KASAN: alloca-out-of-bounds Read in unwind_next_frame

On Fri, Apr 6, 2018 at 6:53 PM, Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> On Fri, Apr 06, 2018 at 05:40:01PM +0200, Dmitry Vyukov wrote:
>> > So at first glance it seemed like a race condition.  However, the
>> > unwinder was only trying to dereference the frame pointer (RBP:
>> > ffff8801b05e67f8), which should have never been poisoned in the first
>> > place.
>> >
>> > So it looks like a bug in the KASAN alloca poisoning.
>>
>> Hi Josh,
>>
>> You seen my previous message, right? Or was it lost somehow?
>>
>> https://groups.google.com/d/msg/syzkaller-bugs/IcKqxHzhmQc/KAL6o7tOCAAJ
>
> Oops, you're right, I missed it.  Seems like we came to the same
> conclusion anyway :-)


The gcc bug is now fixed

#syz invalid