From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, ncardwell@google.com, kuniyu@google.com,
willemb@google.com, netdev@vger.kernel.org,
eric.dumazet@gmail.com,
syzbot+937b5bbb6a815b3e5d0b@syzkaller.appspotmail.com
Subject: Re: [PATCH net] tcp: fix potential race in tcp_v6_syn_recv_sock()
Date: Thu, 19 Feb 2026 22:30:07 +0000 [thread overview]
Message-ID: <177154020754.115050.16114884600252600916.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260217161205.2079883-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Feb 2026 16:12:05 +0000 you wrote:
> Code in tcp_v6_syn_recv_sock() after the call to tcp_v4_syn_recv_sock()
> is done too late.
>
> After tcp_v4_syn_recv_sock(), the child socket is already visible
> from TCP ehash table and other cpus might use it.
>
> Since newinet->pinet6 is still pointing to the listener ipv6_pinfo
> bad things can happen as syzbot found.
>
> [...]
Here is the summary with links:
- [net] tcp: fix potential race in tcp_v6_syn_recv_sock()
https://git.kernel.org/netdev/net/c/858d2a4f67ff
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-02-19 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 16:12 [PATCH net] tcp: fix potential race in tcp_v6_syn_recv_sock() Eric Dumazet
2026-02-17 20:41 ` Kuniyuki Iwashima
2026-02-19 22:30 ` patchwork-bot+netdevbpf [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=177154020754.115050.16114884600252600916.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+937b5bbb6a815b3e5d0b@syzkaller.appspotmail.com \
--cc=willemb@google.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