lkml.org 
[lkml]   [2018]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: KASAN: alloca-out-of-bounds Read in unwind_next_frame
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 :-)

--
Josh

\
 
 \ /
  Last update: 2018-04-06 18:54    [W:0.057 / U:1.768 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site