From: Keith Coleman <keith.coleman@n2servers.com>
To: MaoXiaoyun <tinnycloud@hotmail.com>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: insufficiencies in pv kernel image validation
Date: Mon, 16 May 2011 13:05:18 -0400 [thread overview]
Message-ID: <BANLkTi=97c6Aq3T+eO9rVDBLHYk+YsqV0A@mail.gmail.com> (raw)
In-Reply-To: <BLU157-w25813DF684C02E299E97A9DA8D0@phx.gbl>
2011/5/16 MaoXiaoyun <tinnycloud@hotmail.com>:
> Hi:
>
> Documented in https://bugzilla.redhat.com/show_bug.cgi?id=696927.
>
> [[[ It has been found that xc_try_bzip2_decode() and xc_try_lzma_decode()
> decode
> routines did not properly check for possible buffer size overflow in the
> decoding loop. Specially crafted kernel image file could be created that
> would
> trigger allocation of a small buffer resulting in buffer overflow with user
> supplied data.
>
> Additionally, several integer overflows and lack of error/range checking
> that
> could result in the loader reading its own address space or could lead to an
> infinite loop have been found.
>
> A privileged DomU user could use these flaws to cause denial of service or,
> possibly, execute arbitrary code in Dom0.
>
> Only management domains with 32-bit userland are vulnerable.
> ]]]
>
> The last line of above, what is "management domains"?
> Does Xen 4.0/4.1 suffer this bug?
> And any patches available?
>
Patches were committed to all maintained branches, including xen-3.4,
last Monday.
--
Keith Coleman
next prev parent reply other threads:[~2011-05-16 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY0-MC2-F46jsbFMAv00186193@bay0-mc2-f46.Bay0.hotmail.com>
2011-05-16 16:38 ` insufficiencies in pv kernel image validation MaoXiaoyun
2011-05-16 17:05 ` Keith Coleman [this message]
2011-05-20 14:00 ` Ian Jackson
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='BANLkTi=97c6Aq3T+eO9rVDBLHYk+YsqV0A@mail.gmail.com' \
--to=keith.coleman@n2servers.com \
--cc=tinnycloud@hotmail.com \
--cc=xen-devel@lists.xensource.com \
/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).