From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Li Qiang" <liq3ea@gmail.com>
Cc: Li Qiang <liq3ea@163.com>, Gerd Hoffmann <kraxel@redhat.com>,
QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH 0/7] vhost-user-gpu: fix several security issues
Date: Mon, 10 May 2021 21:25:12 +0200 [thread overview]
Message-ID: <fc38a372-57ad-6c22-c4e8-cfe56ad35d05@redhat.com> (raw)
In-Reply-To: <CAJ+F1CKgZzKzCurGSyQ7s2ZOADgX7BbWgvDVV=ejgthdA3K+pQ@mail.gmail.com>
On 5/5/21 11:35 AM, Marc-André Lureau wrote:
> Hi
>
> On Wed, May 5, 2021 at 1:28 PM Li Qiang <liq3ea@gmail.com
> <mailto:liq3ea@gmail.com>> wrote:
>
> Marc-André Lureau <marcandre.lureau@gmail.com
> <mailto:marcandre.lureau@gmail.com>> 于2021年5月5日周三 下午5:10写道:
> >
> > Hi
> >
> > On Wed, May 5, 2021 at 9:21 AM Li Qiang <liq3ea@163.com
> <mailto:liq3ea@163.com>> wrote:
> >>
> >> These security issue is low severity and is similar with the
> >> virtio-vga/virtio-gpu device. All of them can be triggered by
> >> the guest user.
> >>
> >> Li Qiang (7):
> >> vhost-user-gpu: fix memory disclosure in virgl_cmd_get_capset_info
> >> vhost-user-gpu: fix resource leak in 'vg_resource_create_2d'
> >> vhost-user-gpu: fix memory leak in vg_resource_attach_backing
> >> vhost-user-gpu: fix memory link while calling 'vg_resource_unref'
> >> vhost-user-gpu: fix memory leak in 'virgl_cmd_resource_unref'
> >> vhost-user-gpu: fix memory leak in 'virgl_resource_attach_backing'
> >> vhost-user-gpu: fix OOB write in 'virgl_cmd_get_capset'
> >>
> >> contrib/vhost-user-gpu/vhost-user-gpu.c | 7 +++++++
> >> contrib/vhost-user-gpu/virgl.c | 17 ++++++++++++++++-
> >> 2 files changed, 23 insertions(+), 1 deletion(-)
> >>
> >> --
> >
> >
> > The whole series looks good to me, and applies fixes that were
> done earlier in virtio-gpu.
>
> Do you mean you have merged this series?
> Should I tweak something such as "adding the original fix in
> virtio-gpu"/"better mapping iov cleanup"?
Yes, and please also mention the corresponding CVE (CVE-2021-3544,
CVE-2021-3545, CVE-2021-3546).
>
>
> No I didn't. I was waiting for the answers to Prasad questions, and
> eventually v2.
>
> Then either Gerd or me can queue this imho.
>
> --
> Marc-André Lureau
next prev parent reply other threads:[~2021-05-10 19:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 4:58 [PATCH 0/7] vhost-user-gpu: fix several security issues Li Qiang
2021-05-05 4:58 ` [PATCH 1/7] vhost-user-gpu: fix memory disclosure in virgl_cmd_get_capset_info Li Qiang
2021-05-05 7:23 ` P J P
2021-05-05 9:07 ` Li Qiang
2021-05-06 5:53 ` P J P
2021-05-06 7:49 ` Li Qiang
2021-05-05 4:58 ` [PATCH 2/7] vhost-user-gpu: fix resource leak in 'vg_resource_create_2d' Li Qiang
2021-05-05 7:28 ` P J P
2021-05-05 4:58 ` [PATCH 3/7] vhost-user-gpu: fix memory leak in vg_resource_attach_backing Li Qiang
2021-05-05 7:39 ` P J P
2021-05-05 9:11 ` Li Qiang
2021-05-05 4:58 ` [PATCH 4/7] vhost-user-gpu: fix memory link while calling 'vg_resource_unref' Li Qiang
2021-05-05 7:42 ` P J P
2021-05-05 4:58 ` [PATCH 5/7] vhost-user-gpu: fix memory leak in 'virgl_cmd_resource_unref' Li Qiang
2021-05-05 7:48 ` P J P
2021-05-05 9:14 ` Li Qiang
2021-05-05 4:58 ` [PATCH 6/7] vhost-user-gpu: fix memory leak in 'virgl_resource_attach_backing' Li Qiang
2021-05-05 7:55 ` P J P
2021-05-05 9:07 ` Marc-André Lureau
2021-05-05 9:23 ` Li Qiang
2021-05-05 9:33 ` Marc-André Lureau
2021-05-05 4:58 ` [PATCH 7/7] vhost-user-gpu: fix OOB write in 'virgl_cmd_get_capset' Li Qiang
2021-05-05 7:58 ` P J P
2021-05-05 9:10 ` [PATCH 0/7] vhost-user-gpu: fix several security issues Marc-André Lureau
2021-05-05 9:27 ` Li Qiang
2021-05-05 9:35 ` Marc-André Lureau
2021-05-10 19:25 ` Philippe Mathieu-Daudé [this message]
2021-05-11 2:49 ` Li Qiang
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=fc38a372-57ad-6c22-c4e8-cfe56ad35d05@redhat.com \
--to=philmd@redhat.com \
--cc=kraxel@redhat.com \
--cc=liq3ea@163.com \
--cc=liq3ea@gmail.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.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).