From: Jack Schwartz <jack.schwartz@oracle.com>
To: qemu-devel@nongnu.org, kwolf@redhat.com,
peter.maydell@linaro.org, pjp@fedoraproject.org,
kraxel@redhat.com
Cc: karl.heubaum@oracle.com, konrad.wilk@oracle.com,
mark.kanda@oracle.com, jack.schwartz@oracle.com
Subject: [Qemu-devel] [PATCH 0/1] multiboot.c: Document as fixed against CVE-2018-7550
Date: Wed, 21 Mar 2018 13:53:46 -0700 [thread overview]
Message-ID: <1521665627-5451-1-git-send-email-jack.schwartz@oracle.com> (raw)
Some changes were delivered a few weeks ago that fixed CVE-2018-7550
before that CVE was created. Changeset:
2a8fcd119eb7 ("multiboot: bss_end_addr can be zero")
Shortly after that delivery, a different changeset claimed in its commit
message to fix that CVE, but it really fixed a different one. Changeset:
7cdc61becd09 ("vga: fix region calculation")
PJP says the proper CVE is CVE-2018-7858
https://bugzilla.redhat.com/show_bug.cgi?id=1553402
Not sure what the proper protocol is for getting this all straightened
out, but I would like to help since I delivered the multiboot changes.
This patch set contains an empty patch with a commit message to document
the multiboot changes. Please add it to the repo as you see fit, or let
me know if you need something else from me to resolve this differently.
Note that unless the vga CVE is explained/corrected, people may get
confused when they see different fixes associated with the same CVE.
Thanks,
Jack
Jack Schwartz (1):
multiboot.c: Document as fixed against CVE-2018-7550
--
1.8.3.1
next reply other threads:[~2018-03-21 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 20:53 Jack Schwartz [this message]
2018-03-21 20:53 ` [Qemu-devel] [PATCH 1/1] multiboot.c: Document as fixed against CVE-2018-7550 Jack Schwartz
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=1521665627-5451-1-git-send-email-jack.schwartz@oracle.com \
--to=jack.schwartz@oracle.com \
--cc=karl.heubaum@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mark.kanda@oracle.com \
--cc=peter.maydell@linaro.org \
--cc=pjp@fedoraproject.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).