All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+@syzkaller.appspotmail.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: christophe.gouault@6wind.com, ebiggers3@gmail.com, fw@strlen.de,
	herbert@gondor.apana.org.au, netdev@vger.kernel.org,
	steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com,
	timo.teras@iki.fi
Subject: Re: [PATCH ipsec] xfrm: skip policies marked as dead while rehashing
Date: Tue, 30 Jan 2018 17:59:58 -0800	[thread overview]
Message-ID: <001a114484fc258f34056408d6e1@google.com> (raw)
In-Reply-To: <20180131015954.vdcywjiga6idam53@gmail.com>

> On Sun, Dec 31, 2017 at 08:50:17AM +0100, Steffen Klassert wrote:
>> On Wed, Dec 27, 2017 at 11:25:45PM +0100, Florian Westphal wrote:
>> > syzkaller triggered following KASAN splat:
>> >
>> > BUG: KASAN: slab-out-of-bounds in xfrm_hash_rebuild+0xdbe/0xf00  
>> net/xfrm/xfrm_policy.c:618
>> > read of size 2 at addr ffff8801c8e92fe4 by task kworker/1:1/23 [..]
>> > Workqueue: events xfrm_hash_rebuild [..]
>> >  __asan_report_load2_noabort+0x14/0x20 mm/kasan/report.c:428
>> >  xfrm_hash_rebuild+0xdbe/0xf00 net/xfrm/xfrm_policy.c:618
>> >  process_one_work+0xbbf/0x1b10 kernel/workqueue.c:2112
>> >  worker_thread+0x223/0x1990 kernel/workqueue.c:2246 [..]
>> >
>> > The reproducer triggers:
>> > 1016                 if (error) {
>> > 1017                         list_move_tail(&walk->walk.all, &x->all);
>> > 1018                         goto out;
>> > 1019                 }
>> >
>> > in xfrm_policy_walk() via pfkey (it sets tiny rcv space, dump
>> > callback returns -ENOBUFS).
>> >
>> > In this case, *walk is located the pfkey socket struct, so this socket
>> > becomes visible in the global policy list.
>> >
>> > It looks like this is intentional -- phony walker has walk.dead set to  
>> 1
>> > and all other places skip such "policies".
>> >
>> > Ccing original authors of the two commits that seem to expose this
>> > issue (first patch missed ->dead check, second patch adds pfkey
>> > sockets to policies dumper list).
>> >
>> > Fixes: 880a6fab8f6ba5b ("xfrm: configure policy hash table thresholds  
>> by netlink")
>> > Fixes: 12a169e7d8f4b1c ("ipsec: Put dumpers on the dump list")
>> > Cc: Herbert Xu <herbert@gondor.apana.org.au>
>> > Cc: Timo Teras <timo.teras@iki.fi>
>> > Cc: Christophe Gouault <christophe.gouault@6wind.com>
>> > Reported-by: syzbot  
>> <bot+c028095236fcb6f4348811565b75084c754dc729@syzkaller.appspotmail.com>
>> > Signed-off-by: Florian Westphal <fw@strlen.de>

>> Applied, thanks a lot!


> This crash seems to have stopped occurring, thanks Florian!  Let's tell  
> syzbot
> so that it can start reporting any crashes in this same place again:

> #syz fix: xfrm: skip policies marked as dead while rehashing

Can't find the corresponding bug.


> - Eric

> --
> You received this message because you are subscribed to the Google  
> Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit  
> https://groups.google.com/d/msgid/syzkaller-bugs/20180131015954.vdcywjiga6idam53%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2018-01-31  1:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 20:28 KASAN: slab-out-of-bounds Read in xfrm_hash_rebuild syzbot
2017-12-21 13:48 ` syzbot
2017-12-27 22:25   ` [PATCH ipsec] xfrm: skip policies marked as dead while rehashing Florian Westphal
2017-12-31  7:50     ` Steffen Klassert
2018-01-31  1:59       ` Eric Biggers
2018-01-31  1:59         ` syzbot [this message]
2018-01-31  2:02   ` KASAN: slab-out-of-bounds Read in xfrm_hash_rebuild 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=001a114484fc258f34056408d6e1@google.com \
    --to=syzbot+@syzkaller.appspotmail.com \
    --cc=christophe.gouault@6wind.com \
    --cc=ebiggers3@gmail.com \
    --cc=fw@strlen.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=timo.teras@iki.fi \
    /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.