From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
P J P <ppandit@redhat.com>, Wenxiang Qian <leonwxqian@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [PATCH] ide:atapi: check io_buffer_index in ide_atapi_cmd_reply_end
Date: Tue, 1 Dec 2020 15:30:30 +0000 [thread overview]
Message-ID: <CAFEAcA80QONZVnvf_BVnvFtx7tRX9Zr+7KCCuLJy7wXwppF7gQ@mail.gmail.com> (raw)
In-Reply-To: <0fd8daa2-7ce3-0231-8b95-d498ce900c8e@redhat.com>
On Tue, 1 Dec 2020 at 15:28, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
> About reproducer, Michael asked about CVE-2020-24352 (ati_vga OOB in
> ati_2d_blt) this morning. What happens to reproducers when a CVE is
> assigned, but the bug is marked as "out of the QEMU security boundary"?
Also, why are we assigning CVEs for bugs we don't consider security bugs?
thanks
-- PMM
next prev parent reply other threads:[~2020-12-01 15:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 14:27 [PATCH] ide:atapi: check io_buffer_index in ide_atapi_cmd_reply_end P J P
2020-11-27 13:57 ` P J P
2020-12-01 11:51 ` Paolo Bonzini
2020-12-01 15:00 ` P J P
2020-12-01 15:23 ` Philippe Mathieu-Daudé
2020-12-01 15:30 ` Peter Maydell [this message]
2020-12-01 15:42 ` Paolo Bonzini
2020-12-01 15:30 ` Paolo Bonzini
2020-12-01 15:30 ` Paolo Bonzini
2020-12-02 7:07 ` Markus Armbruster
2020-12-02 13:17 ` P J P
2020-12-02 13:33 ` Paolo Bonzini
2020-12-02 13:36 ` Philippe Mathieu-Daudé
2020-12-03 9:48 ` P J P
2020-12-11 8:23 ` Wenxiang Qian
2020-12-11 8:32 ` Wenxiang Qian
2020-12-11 11:46 ` Paolo Bonzini
2020-12-11 11:45 ` Paolo Bonzini
2020-12-11 14:16 ` P J P
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=CAFEAcA80QONZVnvf_BVnvFtx7tRX9Zr+7KCCuLJy7wXwppF7gQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=jsnow@redhat.com \
--cc=leonwxqian@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=ppandit@redhat.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).