linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qiujun Huang <anenbupt@gmail.com>
To: syzbot <syzbot+cea71eec5d6de256d54d@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, kuba@kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	linux-sctp@vger.kernel.org, marcelo.leitner@gmail.com,
	netdev@vger.kernel.org, nhorman@tuxdriver.com,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	vyasevich@gmail.com
Subject: Re: Re: WARNING: refcount bug in sctp_wfree
Date: Thu, 26 Mar 2020 23:53:24 +0800	[thread overview]
Message-ID: <CADG63jDmhxE0mrbP8-M7LBHcq7bJGdNjxJ3OF-KMdosZxba0QQ@mail.gmail.com> (raw)
In-Reply-To: <000000000000cb35d705a1c3c747@google.com>

[-- Attachment #1: Type: text/plain, Size: 5623 bytes --]

#syz test: upstream, 2c523b34

On Thu, Mar 26, 2020 at 11:38 PM syzbot
<syzbot+cea71eec5d6de256d54d@syzkaller.appspotmail.com> wrote:
>
> > #syz test: upstream
>
> want 2 args (repo, branch), got 10
>
> >
> > On Tue, Mar 10, 2020 at 9:36 AM syzbot
> > <syzbot+cea71eec5d6de256d54d@syzkaller.appspotmail.com> wrote:
> >>
> >> Hello,
> >>
> >> syzbot found the following crash on:
> >>
> >> HEAD commit:    2c523b34 Linux 5.6-rc5
> >> git tree:       upstream
> >> console output: https://syzkaller.appspot.com/x/log.txt?x=155a5f29e00000
> >> kernel config:  https://syzkaller.appspot.com/x/.config?x=a5295e161cd85b82
> >> dashboard link: https://syzkaller.appspot.com/bug?extid=cea71eec5d6de256d54d
> >> compiler:       clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
> >> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=164b5181e00000
> >> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=166dd70de00000
> >>
> >> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> >> Reported-by: syzbot+cea71eec5d6de256d54d@syzkaller.appspotmail.com
> >>
> >> ------------[ cut here ]------------
> >> refcount_t: underflow; use-after-free.
> >> WARNING: CPU: 1 PID: 8668 at lib/refcount.c:28 refcount_warn_saturate+0x15b/0x1a0 lib/refcount.c:28
> >> Kernel panic - not syncing: panic_on_warn set ...
> >> CPU: 1 PID: 8668 Comm: syz-executor779 Not tainted 5.6.0-rc5-syzkaller #0
> >> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> >> Call Trace:
> >>  __dump_stack lib/dump_stack.c:77 [inline]
> >>  dump_stack+0x1e9/0x30e lib/dump_stack.c:118
> >>  panic+0x264/0x7a0 kernel/panic.c:221
> >>  __warn+0x209/0x210 kernel/panic.c:582
> >>  report_bug+0x1ac/0x2d0 lib/bug.c:195
> >>  fixup_bug arch/x86/kernel/traps.c:174 [inline]
> >>  do_error_trap+0xca/0x1c0 arch/x86/kernel/traps.c:267
> >>  do_invalid_op+0x32/0x40 arch/x86/kernel/traps.c:286
> >>  invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1027
> >> RIP: 0010:refcount_warn_saturate+0x15b/0x1a0 lib/refcount.c:28
> >> Code: c7 e4 ff d0 88 31 c0 e8 23 20 b3 fd 0f 0b eb 85 e8 8a 4a e0 fd c6 05 ff 70 b1 05 01 48 c7 c7 10 00 d1 88 31 c0 e8 05 20 b3 fd <0f> 0b e9 64 ff ff ff e8 69 4a e0 fd c6 05 df 70 b1 05 01 48 c7 c7
> >> RSP: 0018:ffffc90001f577d0 EFLAGS: 00010246
> >> RAX: 8c9c9070bbb4e500 RBX: 0000000000000003 RCX: ffff8880938a63c0
> >> RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
> >> RBP: 0000000000000003 R08: ffffffff815e16e6 R09: fffffbfff15db92a
> >> R10: fffffbfff15db92a R11: 0000000000000000 R12: dffffc0000000000
> >> R13: ffff88809de82000 R14: ffff8880a89237c0 R15: 1ffff11013be52b0
> >>  sctp_wfree+0x3b1/0x710 net/sctp/socket.c:9111
> >>  skb_release_head_state+0xfb/0x210 net/core/skbuff.c:651
> >>  skb_release_all net/core/skbuff.c:662 [inline]
> >>  __kfree_skb+0x22/0x1c0 net/core/skbuff.c:678
> >>  sctp_chunk_destroy net/sctp/sm_make_chunk.c:1454 [inline]
> >>  sctp_chunk_put+0x17b/0x200 net/sctp/sm_make_chunk.c:1481
> >>  __sctp_outq_teardown+0x80a/0x9d0 net/sctp/outqueue.c:257
> >>  sctp_association_free+0x21e/0x7c0 net/sctp/associola.c:339
> >>  sctp_cmd_delete_tcb net/sctp/sm_sideeffect.c:930 [inline]
> >>  sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1318 [inline]
> >>  sctp_side_effects net/sctp/sm_sideeffect.c:1185 [inline]
> >>  sctp_do_sm+0x3c01/0x5560 net/sctp/sm_sideeffect.c:1156
> >>  sctp_primitive_ABORT+0x93/0xc0 net/sctp/primitive.c:104
> >>  sctp_close+0x231/0x770 net/sctp/socket.c:1512
> >>  inet_release+0x135/0x180 net/ipv4/af_inet.c:427
> >>  __sock_release net/socket.c:605 [inline]
> >>  sock_close+0xd8/0x260 net/socket.c:1283
> >>  __fput+0x2d8/0x730 fs/file_table.c:280
> >>  task_work_run+0x176/0x1b0 kernel/task_work.c:113
> >>  exit_task_work include/linux/task_work.h:22 [inline]
> >>  do_exit+0x5ef/0x1f80 kernel/exit.c:801
> >>  do_group_exit+0x15e/0x2c0 kernel/exit.c:899
> >>  __do_sys_exit_group+0x13/0x20 kernel/exit.c:910
> >>  __se_sys_exit_group+0x10/0x10 kernel/exit.c:908
> >>  __x64_sys_exit_group+0x37/0x40 kernel/exit.c:908
> >>  do_syscall_64+0xf3/0x1b0 arch/x86/entry/common.c:294
> >>  entry_SYSCALL_64_after_hwframe+0x49/0xbe
> >> RIP: 0033:0x43ef98
> >> Code: Bad RIP value.
> >> RSP: 002b:00007ffcc7e7c398 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
> >> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ef98
> >> RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
> >> RBP: 00000000004be7a8 R08: 00000000000000e7 R09: ffffffffffffffd0
> >> R10: 000000002059aff8 R11: 0000000000000246 R12: 0000000000000001
> >> R13: 00000000006d01a0 R14: 0000000000000000 R15: 0000000000000000
> >> Kernel Offset: disabled
> >> Rebooting in 86400 seconds..
> >>
> >>
> >> ---
> >> This bug is generated by a bot. It may contain errors.
> >> See https://goo.gl/tpsmEJ for more information about syzbot.
> >> syzbot engineers can be reached at syzkaller@googlegroups.com.
> >>
> >> syzbot will keep track of this bug report. See:
> >> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> >> syzbot can test patches for this bug, for details see:
> >> https://goo.gl/tpsmEJ#testing-patches
> >
> > --
> > 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/CADG63jDCTdgSxDRsN_9e3fKCAv5VduS5NNKWmqjByZ%3D4sT%2BHLQ%40mail.gmail.com.

[-- Attachment #2: 0001-sctp-fix-refcount-bug-in-sctp_wfree.patch --]
[-- Type: application/octet-stream, Size: 3516 bytes --]

From 65f600e85a8dc6e6bcbab69e4111e83041f22c32 Mon Sep 17 00:00:00 2001
From: Qiujun Huang <hqjagain@gmail.com>
Date: Thu, 26 Mar 2020 23:22:38 +0800
Subject: [PATCH] sctp: fix refcount bug in sctp_wfree

We should iterate over the datamsgs to modify
all chunks(skbs) to newsk.

The following case cause the bug:
for the trouble SKB, it was in outq->transmitted list

sctp_outq_sack
        sctp_check_transmitted
                SKB was moved to outq->sacked list
        then throw away the sack queue
                SKB was deleted from outq->sacked
(but it was held by datamsg at sctp_datamsg_to_asoc
So, sctp_wfree was not called here)

then migrate happened

        sctp_for_each_tx_datachunk(
        sctp_clear_owner_w);
        sctp_assoc_migrate();
        sctp_for_each_tx_datachunk(
        sctp_set_owner_w);
SKB was not in the outq, and was not changed to newsk

finally

__sctp_outq_teardown
        sctp_chunk_put (for another skb)
                sctp_datamsg_put
                        __kfree_skb(msg->frag_list)
                                sctp_wfree (for SKB)
	SKB->sk was still oldsk (skb->sk != asoc->base.sk).

Reported-and-tested-by:syzbot+cea71eec5d6de256d54d@syzkaller.appspotmail.com
Signed-off-by: Qiujun Huang <hqjagain@gmail.com>
---
 net/sctp/socket.c | 30 ++++++++++++++++++++++--------
 1 file changed, 22 insertions(+), 8 deletions(-)

diff --git a/net/sctp/socket.c b/net/sctp/socket.c
index 1b56fc440606..75acbd5d4597 100644
--- a/net/sctp/socket.c
+++ b/net/sctp/socket.c
@@ -147,29 +147,43 @@ static void sctp_clear_owner_w(struct sctp_chunk *chunk)
 	skb_orphan(chunk->skb);
 }
 
+#define traverse_and_process()	\
+do {				\
+	msg = chunk->msg;	\
+	if (msg == prev_msg)	\
+		continue;	\
+	list_for_each_entry(c, &msg->chunks, frag_list) {	\
+		if ((clear && asoc->base.sk == c->skb->sk) ||	\
+		    (!clear && asoc->base.sk != c->skb->sk))	\
+		    cb(c);	\
+	}			\
+} while (0)
+
 static void sctp_for_each_tx_datachunk(struct sctp_association *asoc,
+				       bool clear,
 				       void (*cb)(struct sctp_chunk *))
 
 {
+	struct sctp_datamsg *msg, *prev_msg = NULL;
 	struct sctp_outq *q = &asoc->outqueue;
+	struct sctp_chunk *chunk, *c;
 	struct sctp_transport *t;
-	struct sctp_chunk *chunk;
 
 	list_for_each_entry(t, &asoc->peer.transport_addr_list, transports)
 		list_for_each_entry(chunk, &t->transmitted, transmitted_list)
-			cb(chunk);
+			traverse_and_process();
 
 	list_for_each_entry(chunk, &q->retransmit, transmitted_list)
-		cb(chunk);
+		traverse_and_process();
 
 	list_for_each_entry(chunk, &q->sacked, transmitted_list)
-		cb(chunk);
+		traverse_and_process();
 
 	list_for_each_entry(chunk, &q->abandoned, transmitted_list)
-		cb(chunk);
+		traverse_and_process();
 
 	list_for_each_entry(chunk, &q->out_chunk_list, list)
-		cb(chunk);
+		traverse_and_process();
 }
 
 static void sctp_for_each_rx_skb(struct sctp_association *asoc, struct sock *sk,
@@ -9574,9 +9588,9 @@ static int sctp_sock_migrate(struct sock *oldsk, struct sock *newsk,
 	 * paths won't try to lock it and then oldsk.
 	 */
 	lock_sock_nested(newsk, SINGLE_DEPTH_NESTING);
-	sctp_for_each_tx_datachunk(assoc, sctp_clear_owner_w);
+	sctp_for_each_tx_datachunk(assoc, true, sctp_clear_owner_w);
 	sctp_assoc_migrate(assoc, newsk);
-	sctp_for_each_tx_datachunk(assoc, sctp_set_owner_w);
+	sctp_for_each_tx_datachunk(assoc, false, sctp_set_owner_w);
 
 	/* If the association on the newsk is already closed before accept()
 	 * is called, set RCV_SHUTDOWN flag.
-- 
2.17.1


  reply	other threads:[~2020-03-26 15:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  1:35 WARNING: refcount bug in sctp_wfree syzbot
2020-03-10  9:39 ` syzbot
2020-03-10 16:01   ` Kees Cook
2020-03-16 15:51     ` Will Deacon
2020-03-16 16:25       ` Qiujun Huang
2020-03-10 16:45 ` 黄秋钧
2020-03-11 15:00 ` Qiujun Huang
2020-03-14  2:51   ` Qiujun Huang
2020-03-14  2:59     ` Qiujun Huang
2020-03-14  2:54 ` Qiujun Huang
2020-03-14  2:55   ` Qiujun Huang
2020-03-14  4:08     ` syzbot
2020-03-14  4:04   ` syzbot
2020-03-14  5:10 ` Qiujun Huang
2020-03-14  9:03   ` syzbot
2020-03-15  7:59 ` Qiujun Huang
2020-03-15  8:12   ` syzbot
2020-03-20 11:11 ` Qiujun Huang
2020-03-20 14:28   ` syzbot
2020-03-22  4:11 ` Qiujun Huang
2020-03-22  4:39   ` syzbot
2020-03-22  6:41     ` Qiujun Huang
2020-03-22  7:18       ` syzbot
2020-03-26 15:38 ` Qiujun Huang
2020-03-26 15:38   ` syzbot
2020-03-26 15:38   ` syzbot
2020-03-26 15:53     ` Qiujun Huang [this message]
2020-03-26 15:53       ` syzbot
2020-03-26 16:17         ` Qiujun Huang
2020-03-26 21:25           ` syzbot

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=CADG63jDmhxE0mrbP8-M7LBHcq7bJGdNjxJ3OF-KMdosZxba0QQ@mail.gmail.com \
    --to=anenbupt@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=syzbot+cea71eec5d6de256d54d@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vyasevich@gmail.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 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).