From: patchwork-bot+netdevbpf@kernel.org
To: Artem Chernyshev <artem.chernyshev@red-soft.ru>
Cc: vdasa@vmware.com, sgarzare@redhat.com, pv-drivers@vmware.com,
bryantan@vmware.com, kuba@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH v4] net: vmw_vsock: vmci: Check memcpy_from_msg()
Date: Fri, 09 Dec 2022 08:50:15 +0000 [thread overview]
Message-ID: <167057581586.8412.7293501811642337752.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221206065834.1093081-1-artem.chernyshev@red-soft.ru>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 6 Dec 2022 09:58:34 +0300 you wrote:
> vmci_transport_dgram_enqueue() does not check the return value
> of memcpy_from_msg(). If memcpy_from_msg() fails, it is possible that
> uninitialized memory contents are sent unintentionally instead of user's
> message in the datagram to the destination. Return with an error if
> memcpy_from_msg() fails.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> [...]
Here is the summary with links:
- [v4] net: vmw_vsock: vmci: Check memcpy_from_msg()
https://git.kernel.org/netdev/net/c/44aa5a6dba82
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:[~2022-12-09 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 22:58 [PATCH] net: vmw_vsock: vmci: Check memcpy_from_msg() Artem Chernyshev
2022-12-03 1:17 ` Vishnu Dasa
2022-12-03 7:56 ` Artem Chernyshev
2022-12-03 8:33 ` [PATCH v2] " Artem Chernyshev
2022-12-05 9:47 ` Stefano Garzarella
2022-12-05 11:22 ` Artem Chernyshev
2022-12-05 11:52 ` [PATCH v3] " Artem Chernyshev
2022-12-05 13:06 ` Stefano Garzarella
2022-12-05 23:03 ` Vishnu Dasa
2022-12-06 6:52 ` Artem Chernyshev
2022-12-06 6:58 ` [PATCH v4] " Artem Chernyshev
2022-12-09 8:50 ` 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=167057581586.8412.7293501811642337752.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=artem.chernyshev@red-soft.ru \
--cc=bryantan@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=sgarzare@redhat.com \
--cc=vdasa@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
/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