From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+9d1d9866b0b8ee6e0a8c@syzkaller.appspotmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
syzkaller-bugs@googlegroups.com,
Thomas Gleixner <tglx@linutronix.de>,
the arch/x86 maintainers <x86@kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: KASAN: alloca-out-of-bounds Read in unwind_next_frame
Date: Fri, 6 Apr 2018 11:53:38 -0500 [thread overview]
Message-ID: <20180406165338.oa5wmjtknauehafp@treble> (raw)
In-Reply-To: <CACT4Y+Zi3cBfjao_VE6ugOXosuCXWoJ58PfuZdYbckfOLzN09A@mail.gmail.com>
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
next prev parent reply other threads:[~2018-04-06 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 0:02 KASAN: alloca-out-of-bounds Read in unwind_next_frame syzbot
2018-04-06 9:09 ` Dmitry Vyukov
2018-04-06 15:36 ` Josh Poimboeuf
2018-04-06 15:40 ` Dmitry Vyukov
2018-04-06 16:53 ` Josh Poimboeuf [this message]
2018-04-13 11:16 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180406165338.oa5wmjtknauehafp@treble \
--to=jpoimboe@redhat.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=syzbot+9d1d9866b0b8ee6e0a8c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).