From: patchwork-bot+netdevbpf@kernel.org
To: Minh Nguyen <minhnguyen.080505@gmail.com>
Cc: pabeni@redhat.com, bryan-bt.tan@broadcom.com,
sgarzare@redhat.com, vishnu.dasa@broadcom.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
horms@kernel.org, bcm-kernel-feedback-list@broadcom.com,
netdev@vger.kernel.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v4] vsock/vmci: fix UAF when peer resets connection during handshake
Date: Thu, 21 May 2026 02:20:07 +0000 [thread overview]
Message-ID: <177933000715.3834961.4605675753542747762.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260519102310.237181-1-minhnguyen.080505@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 19 May 2026 17:23:10 +0700 you wrote:
> vmci_transport_recv_connecting_server() returned err = 0 for a peer
> RST in its default switch arm:
>
> err = pkt->type == VMCI_TRANSPORT_PACKET_TYPE_RST ? 0 : -EINVAL;
>
> That made vmci_transport_recv_listen() skip vsock_remove_pending(),
> leaving the pending socket on the listener's pending_links with
> sk_state = TCP_CLOSE while destroy: still dropped the explicit
> reference taken before schedule_delayed_work().
>
> [...]
Here is the summary with links:
- [net,v4] vsock/vmci: fix UAF when peer resets connection during handshake
https://git.kernel.org/netdev/net/c/99e22ddf4edb
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-05-21 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 10:23 [PATCH net v4] vsock/vmci: fix UAF when peer resets connection during handshake Minh Nguyen
2026-05-20 13:51 ` Bryan Tan
2026-05-21 2:20 ` 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=177933000715.3834961.4605675753542747762.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minhnguyen.080505@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=vishnu.dasa@broadcom.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