From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Дмитрий Фролов" <frolov@swemel.ru>
Cc: mst@redhat.com, sdl.qemu@linuxtesting.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/net/virtio-net.c: fix crash in iov_copy()
Date: Tue, 11 Jun 2024 15:08:08 +0100 [thread overview]
Message-ID: <871q53zi5z.fsf@draig.linaro.org> (raw)
In-Reply-To: <a2a6e83e-fb47-4de1-a807-81843092c3fa@swemel.ru> ("Дмитрий Фролов"'s message of "Tue, 11 Jun 2024 15:33:12 +0300")
Дмитрий Фролов <frolov@swemel.ru> writes:
> ping
>
> https://patchew.org/QEMU/20240527133140.218300-2-frolov@swemel.ru/
>
> On 27.05.2024 16:31, Dmitry Frolov wrote:
>> A crash found while fuzzing device virtio-net-socket-check-used.
>> Assertion "offset == 0" in iov_copy() fails if less than guest_hdr_len bytes
>> were transmited.
>>
>> Signed-off-by: Dmitry Frolov <frolov@swemel.ru>
>> ---
>> hw/net/virtio-net.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
>> index 24e5e7d347..603b80a50a 100644
>> --- a/hw/net/virtio-net.c
>> +++ b/hw/net/virtio-net.c
>> @@ -2783,6 +2783,12 @@ static int32_t virtio_net_flush_tx(VirtIONetQueue *q)
>> */
>> assert(n->host_hdr_len <= n->guest_hdr_len);
>> if (n->host_hdr_len != n->guest_hdr_len) {
>> + if (iov_size(out_sg, out_num) < n->guest_hdr_len) {
>> + virtio_error(vdev, "virtio-net header is invalid");
>> + virtqueue_detach_element(q->tx_vq, elem, 0);
>> + g_free(elem);
>> + return -EINVAL;
>> + }
Isn't this basically another case for goto detach?
Although the use of goto's here is a bit of a code smell. I wonder if
there is any way to better structure this function and take care of the
auto-freeing of elements?
>> unsigned sg_num = iov_copy(sg, ARRAY_SIZE(sg),
>> out_sg, out_num,
>> 0, n->host_hdr_len);
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2024-06-11 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 13:31 [PATCH] hw/net/virtio-net.c: fix crash in iov_copy() Dmitry Frolov
2024-06-11 12:33 ` Дмитрий Фролов
2024-06-11 14:08 ` Alex Bennée [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=871q53zi5z.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=frolov@swemel.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sdl.qemu@linuxtesting.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;
as well as URLs for NNTP newsgroup(s).