From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+ba535cb417f106327741@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [sctp?] BUG: corrupted list in sctp_destroy_sock
Date: Fri, 7 Nov 2025 08:35:16 +0800 [thread overview]
Message-ID: <20251107003518.8936-1-hdanton@sina.com> (raw)
In-Reply-To: <690d2185.a70a0220.22f260.000e.GAE@google.com>
> Date: Thu, 06 Nov 2025 14:30:29 -0800
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 1a2352ad82b5 Merge git://git.kernel.org/pub/scm/linux/kern..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1110fe7c580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=810aeb811fb1cca1
> dashboard link: https://syzkaller.appspot.com/bug?extid=ba535cb417f106327741
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12ff9704580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11372bcd980000
#syz test net-next main
--- x/net/sctp/socket.c
+++ y/net/sctp/socket.c
@@ -4895,6 +4895,7 @@ static struct sock *sctp_clone_sock(stru
sk_sockets_allocated_inc(newsk);
sock_prot_inuse_add(sock_net(sk), newsk->sk_prot, 1);
+ newsp->do_auto_asconf = 0;
err = sctp_sock_migrate(sk, newsk, asoc, type);
if (err)
goto out_release;
--
next prev parent reply other threads:[~2025-11-07 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 22:30 [syzbot] [sctp?] BUG: corrupted list in sctp_destroy_sock syzbot
2025-11-07 0:35 ` Hillf Danton [this message]
2025-11-07 2:11 ` 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=20251107003518.8936-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+ba535cb417f106327741@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox