From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michal Luczaj <mhal@rbox.co>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org,
syzbot+9d55b199192a4be7d02c@syzkaller.appspotmail.com
Subject: Re: [PATCH net 0/2] vsock: null-ptr-deref when SO_LINGER enabled
Date: Mon, 24 Feb 2025 16:14:13 -0500 [thread overview]
Message-ID: <20250224161404-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250204-vsock-linger-nullderef-v1-0-6eb1760fa93e@rbox.co>
On Tue, Feb 04, 2025 at 01:29:51AM +0100, Michal Luczaj wrote:
> syzbot pointed out that a recent patching of a use-after-free introduced a
> null-ptr-deref. This series fixes the problem and adds a test.
>
> Fixes fcdd2242c023 ("vsock: Keep the binding until socket destruction").
>
> Signed-off-by: Michal Luczaj <mhal@rbox.co>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> Michal Luczaj (2):
> vsock: Orphan socket after transport release
> vsock/test: Add test for SO_LINGER null ptr deref
>
> net/vmw_vsock/af_vsock.c | 3 ++-
> tools/testing/vsock/vsock_test.c | 41 ++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 43 insertions(+), 1 deletion(-)
> ---
> base-commit: 0e6dc66b5c5fa186a9f96c66421af74212ebcf66
> change-id: 20250203-vsock-linger-nullderef-cbe4402ad306
>
> Best regards,
> --
> Michal Luczaj <mhal@rbox.co>
>
prev parent reply other threads:[~2025-02-24 21:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 0:29 [PATCH net 0/2] vsock: null-ptr-deref when SO_LINGER enabled Michal Luczaj
2025-02-04 0:29 ` [PATCH net 1/2] vsock: Orphan socket after transport release Michal Luczaj
2025-02-04 10:32 ` Stefano Garzarella
2025-02-04 15:44 ` Luigi Leonardi
2025-02-04 16:00 ` Stefano Garzarella
2025-02-05 0:11 ` Michal Luczaj
2025-02-04 23:59 ` Michal Luczaj
2025-02-04 0:29 ` [PATCH net 2/2] vsock/test: Add test for SO_LINGER null ptr deref Michal Luczaj
2025-02-04 10:48 ` Stefano Garzarella
2025-02-05 11:20 ` Michal Luczaj
2025-02-10 10:18 ` Stefano Garzarella
2025-03-07 9:49 ` Michal Luczaj
2025-03-10 15:24 ` Stefano Garzarella
2025-03-14 15:25 ` Michal Luczaj
2025-03-20 11:31 ` Stefano Garzarella
2025-03-25 13:22 ` Michal Luczaj
2025-04-01 10:32 ` Stefano Garzarella
2025-04-03 22:06 ` Michal Luczaj
2025-04-11 13:21 ` Stefano Garzarella
2025-04-11 14:43 ` vsock broken after connect() returns EINTR (was Re: [PATCH net 2/2] vsock/test: Add test for SO_LINGER null ptr deref) Michal Luczaj
2025-04-15 13:07 ` Stefano Garzarella
2025-07-25 9:06 ` Michal Luczaj
2025-11-18 10:14 ` Stefano Garzarella
2025-11-18 22:02 ` Michal Luczaj
2025-04-11 14:44 ` bytes_unsent forever elevated " Michal Luczaj
2025-04-15 13:18 ` Stefano Garzarella
2025-04-11 14:46 ` connect() disconnects TCP_ESTABLISHED " Michal Luczaj
2025-04-15 13:33 ` Stefano Garzarella
2025-02-04 14:45 ` [PATCH net 0/2] vsock: null-ptr-deref when SO_LINGER enabled Luigi Leonardi
2025-02-24 21:14 ` Michael S. Tsirkin [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=20250224161404-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=syzbot+9d55b199192a4be7d02c@syzkaller.appspotmail.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.