From: sashiko-bot@kernel.org
To: "Ilia Gavrilov" <Ilia.Gavrilov@infotecs.ru>
Cc: virtualization@lists.linux.dev,
"Eugenio Perez" <eperezma@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH net] vsock: Fix memory leak in vmci_transport_recv_dgram_cb()
Date: Wed, 07 Oct 2026 14:53:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-163127@kernel.org> (raw)
In-Reply-To: <20261007143716.1984702-1-Ilia.Gavrilov@infotecs.ru>
> During the closure of a datagram socket, the vmci_transport_recv_dgram_cb()
> function may be called, which will add the packets
> to the socket's backlog; then, after the receive queue is cleared,
> the __release_sock() function will move the packet back from the socket's
> backlog to the receive queue, which will lead to a memory leak.
>
> sock_close
> __sock_release
> __vsock_release
> // take ownership by user-space
> lock_sock_nested
> sock_set_flag(sk, SOCK_DEAD)
> vmci_transport_release
> vmci_dispatch_dgs
> vmci_datagram_invoke_guest_handler
> [ ... ]
> Found by InfoTeCS on behalf of Linux Verification Center
> (linuxtesting.org) with Syzkaller.
>
> Fixes: d021c344051a ("VSOCK: Introduce VM Sockets")
> Signed-off-by: Ilia Gavrilov <Ilia.Gavrilov@infotecs.ru>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261007143716.1984702-1-Ilia.Gavrilov@infotecs.ru?part=1
next prev parent reply other threads:[~2026-10-07 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 14:37 [PATCH net] vsock: Fix memory leak in vmci_transport_recv_dgram_cb() Ilia Gavrilov
2026-10-07 14:53 ` sashiko-bot [this message]
2026-10-08 10:16 ` Stefano Garzarella
-- strict thread matches above, loose matches on Subject: below --
2026-10-08 14:38 Ilia Gavrilov
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=sashiko-outbox-163127@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Ilia.Gavrilov@infotecs.ru \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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