From: Eric Biggers <ebiggers3@gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: syzbot
<bot+68bf59b49142965d6454163d7341e617a90139dc@syzkaller.appspotmail.com>,
davem@davemloft.net, herbert@gondor.apana.org.au,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: stack-out-of-bounds Read in xfrm_state_find (3)
Date: Tue, 12 Dec 2017 13:00:31 -0800 [thread overview]
Message-ID: <20171212210031.GC185376@gmail.com> (raw)
In-Reply-To: <20171201072743.47ztbmrql7ub327u@gauss3.secunet.de>
Hi Steffen,
On Fri, Dec 01, 2017 at 08:27:43AM +0100, Steffen Klassert wrote:
> On Wed, Nov 22, 2017 at 08:05:00AM -0800, syzbot wrote:
> > syzkaller has found reproducer for the following crash on
> > 0c86a6bd85ff0629cd2c5141027fc1c8bb6cde9c
> > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
> > compiler: gcc (GCC) 7.1.1 20170620
> > .config is attached
> > Raw console output is attached.
> > C reproducer is attached
> > syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> > for information about syzkaller reproducers
> >
> >
> > BUG: KASAN: stack-out-of-bounds in xfrm_state_find+0x30fc/0x3230
> > net/xfrm/xfrm_state.c:1051
> > Read of size 4 at addr ffff8801ccaa7af8 by task syzkaller231684/3045
>
> The patch below should fix this. I plan to apply it to the ipsec tree
> after some advanced testing.
>
> Subject: [PATCH RFC] xfrm: Fix stack-out-of-bounds with misconfigured transport
> mode policies.
>
Are you still planning to apply this? syzbot is still hitting this bug.
Eric
next prev parent reply other threads:[~2017-12-12 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 17:22 KASAN: stack-out-of-bounds Read in xfrm_state_find (3) syzbot
2017-11-22 16:05 ` syzbot
2017-12-01 7:27 ` Steffen Klassert
2017-12-01 8:15 ` Dmitry Vyukov
2017-12-12 21:00 ` Eric Biggers [this message]
2017-12-13 5:18 ` Steffen Klassert
2018-01-30 21:28 ` Eric Biggers
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=20171212210031.GC185376@gmail.com \
--to=ebiggers3@gmail.com \
--cc=bot+68bf59b49142965d6454163d7341e617a90139dc@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.