All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9d2a6ef56c3805144bf0@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
	 hdanton@sina.com, horms@kernel.org, kuba@kernel.org,
	kuniyu@google.com,  linux-kernel@vger.kernel.org,
	ncardwell@google.com, netdev@vger.kernel.org,  pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in tcp_prune_ofo_queue
Date: Tue, 15 Jul 2025 17:55:02 -0700	[thread overview]
Message-ID: <6876f866.a00a0220.105e77.0001.GAE@google.com> (raw)
In-Reply-To: <6876cc3c.a00a0220.3af5df.000a.GAE@google.com>

syzbot has bisected this issue to:

commit 1d2fbaad7cd8cc96899179f9898ad2787a15f0a0
Author: Eric Dumazet <edumazet@google.com>
Date:   Fri Jul 11 11:40:05 2025 +0000

    tcp: stronger sk_rcvbuf checks

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13b7098c580000
start commit:   55e8757c6962 Merge branch 'net-mctp-improved-bind-handling'
git tree:       net-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1077098c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17b7098c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f8235fb7e74dd7f6
dashboard link: https://syzkaller.appspot.com/bug?extid=9d2a6ef56c3805144bf0
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12494382580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=103327d4580000

Reported-by: syzbot+9d2a6ef56c3805144bf0@syzkaller.appspotmail.com
Fixes: 1d2fbaad7cd8 ("tcp: stronger sk_rcvbuf checks")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2025-07-16  0:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 21:46 [syzbot] [net?] KASAN: slab-use-after-free Read in tcp_prune_ofo_queue syzbot
2025-07-16  0:44 ` Hillf Danton
2025-07-16  1:11   ` syzbot
2025-07-16  0:55 ` syzbot [this message]

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=6876f866.a00a0220.105e77.0001.GAE@google.com \
    --to=syzbot+9d2a6ef56c3805144bf0@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=hdanton@sina.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.