From: P J P <ppandit@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, peter.maydell@linaro.org, mst@redhat.com,
liq3ea@gmail.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2 for 3.1 0/4] Fix possible OOB during queuing packets
Date: Fri, 30 Nov 2018 14:48:19 +0530 (IST) [thread overview]
Message-ID: <nycvar.YSQ.7.76.1811301446050.9903@xnncv> (raw)
In-Reply-To: <44516b60-dafd-70e3-1638-ea38a804c8a4@redhat.com>
+-- On Thu, 29 Nov 2018, Eric Blake wrote --+
| How important is this for 3.1? We've missed -rc3. Is this CVE quality
| because of a guest being able to cause mayhem by intentionally getting into
| this condition (in which case, we need it, as well as a CVE assigned)? Is it
| pre-existing in 3.0 at which point waiting for 4.0 is no worse off than what
| we already are?
It is a revised patch to fix 'CVE-2018-17963' issue. Earlier patch was
included in -rc0.
$ git tag --contains 1592a9947036d60dde5404204a5d45975133caf5
v3.1.0-rc0
v3.1.0-rc1
v3.1.0-rc2
v3.1.0-rc3
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2018-11-30 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 12:14 [Qemu-devel] [PATCH V2 for 3.1 0/4] Fix possible OOB during queuing packets Jason Wang
2018-11-29 12:14 ` [Qemu-devel] [PATCH V2 for 3.1 1/4] net: drop too large packet early Jason Wang
2018-11-29 12:14 ` [Qemu-devel] [PATCH V2 for 3.1 2/4] virtio-net-test: remove unused macro Jason Wang
2018-11-29 12:14 ` [Qemu-devel] [PATCH V2 for 3.1 3/4] virtio-net-test: accept variable length argument in pci_test_start() Jason Wang
2018-11-29 12:14 ` [Qemu-devel] [PATCH V2 for 3.1 4/4] virtio-net-test: add large tx buffer test Jason Wang
2018-11-29 13:53 ` Thomas Huth
2018-11-29 14:05 ` [Qemu-devel] [PATCH V2 for 3.1 0/4] Fix possible OOB during queuing packets Eric Blake
2018-11-30 9:18 ` P J P [this message]
2018-11-30 13:04 ` Jason Wang
2018-11-30 13:29 ` Daniel P. Berrangé
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=nycvar.YSQ.7.76.1811301446050.9903@xnncv \
--to=ppandit@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=liq3ea@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).