From: patchwork-bot+netdevbpf@kernel•org
To: Hyunwoo Kim <v4bel@theori•io>
Cc: ralf@linux-mips•org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, kuniyu@amazon•com,
imv4bel@gmail•com, linux-hams@vger•kernel.org,
netdev@vger•kernel.org,
syzbot+caa188bdfc1eeafeb418@syzkaller•appspotmail.com
Subject: Re: [PATCH v4] netrom: Fix use-after-free caused by accept on already connected socket
Date: Mon, 30 Jan 2023 07:40:16 +0000 [thread overview]
Message-ID: <167506441623.19672.3737671367502579587.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230127023250.GA71840@ubuntu>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Thu, 26 Jan 2023 18:32:50 -0800 you wrote:
> If you call listen() and accept() on an already connect()ed
> AF_NETROM socket, accept() can successfully connect.
> This is because when the peer socket sends data to sendmsg,
> the skb with its own sk stored in the connected socket's
> sk->sk_receive_queue is connected, and nr_accept() dequeues
> the skb waiting in the sk->sk_receive_queue.
>
> [...]
Here is the summary with links:
- [v4] netrom: Fix use-after-free caused by accept on already connected socket
https://git.kernel.org/netdev/net/c/611792920925
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:[~2023-01-30 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 2:32 [PATCH v4] netrom: Fix use-after-free caused by accept on already connected socket Hyunwoo Kim
2023-01-27 16:54 ` Kuniyuki Iwashima
2023-01-30 7:40 ` 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=167506441623.19672.3737671367502579587.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=imv4bel@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kuniyu@amazon$(echo .)com \
--cc=linux-hams@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=ralf@linux-mips$(echo .)org \
--cc=syzbot+caa188bdfc1eeafeb418@syzkaller$(echo .)appspotmail.com \
--cc=v4bel@theori$(echo .)io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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