From: Jack Schwartz <jack.schwartz@oracle.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, anatol.pomozov@gmail.com, ppandit@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/5] multiboot: Reject kernels exceeding the address space
Date: Wed, 14 Mar 2018 22:19:27 -0700 [thread overview]
Message-ID: <4ab6eff1-f4c2-1e04-5fa8-cc71c3bf308d@oracle.com> (raw)
In-Reply-To: <20180314173213.18563-2-kwolf@redhat.com>
Hi Kevin.
My comments are inline...
On 2018-03-14 10:32, Kevin Wolf wrote:
> The code path with a manually set mh_load_addr in the Multiboot header
> checks that load_end_addr <= load_addr, but the path where load_end_addr
> is automatically detected if 0 is given in the header misses the
> corresponding check.
1) The code checks that load_end_addr >= load_addr (before letting it
through).
2) load_end_addr is used only when it is read in as non-zero, so no
check is needed if zero. (It gets debug-printed even when zero, but is
used only to calculate mb_load_size and only when non-zero.)
> If the kernel binary size is larger than can fit in
> the address space after load_addr, we ended up with a kernel_size that
> is smaller than load_size, which means that we read the file into a too
> small buffer.
>
> Add a check to reject kernel files with such Multiboot headers.
Code itself looks fine.
Modulo above comments:
Reviewed-by: Jack Schwartz <jack.schwartz@oracle.com>
Thanks,
Jack
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> hw/i386/multiboot.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/i386/multiboot.c b/hw/i386/multiboot.c
> index b9064264d8..1e215bf8d3 100644
> --- a/hw/i386/multiboot.c
> +++ b/hw/i386/multiboot.c
> @@ -247,6 +247,10 @@ int load_multiboot(FWCfgState *fw_cfg,
> }
> mb_load_size = kernel_file_size - mb_kernel_text_offset;
> }
> + if (mb_load_size > UINT32_MAX - mh_load_addr) {
> + error_report("kernel does not fit in address space");
> + exit(1);
> + }
> if (mh_bss_end_addr) {
> if (mh_bss_end_addr < (mh_load_addr + mb_load_size)) {
> error_report("invalid bss_end_addr address");
next prev parent reply other threads:[~2018-03-15 5:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 17:32 [Qemu-devel] [PATCH 0/5] multiboot: Fix buffer overflow on invalid kernels Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 1/5] multiboot: Reject kernels exceeding the address space Kevin Wolf
2018-03-15 5:19 ` Jack Schwartz [this message]
2018-03-15 15:54 ` Kevin Wolf
2018-03-15 16:55 ` Jack Schwartz
2018-03-15 17:18 ` Kevin Wolf
2018-03-15 19:50 ` Jack Schwartz
2018-03-14 17:32 ` [Qemu-devel] [PATCH 2/5] multiboot: Check validity of mh_header_addr Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 3/5] tests/multiboot: Test exit code for every qemu run Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 4/5] tests/multiboot: Add tests for the a.out kludge Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 5/5] tests/multiboot: Add .gitignore Kevin Wolf
2018-03-14 17:43 ` Eric Blake
2018-03-14 17:50 ` Eric Blake
2018-03-15 5:19 ` [Qemu-devel] [PATCH 0/5] multiboot: Fix buffer overflow on invalid kernels 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=4ab6eff1-f4c2-1e04-5fa8-cc71c3bf308d@oracle.com \
--to=jack.schwartz@oracle.com \
--cc=anatol.pomozov@gmail.com \
--cc=kwolf@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).