From: Shaun Reitan <mailinglists@unix-scripts.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] fs: pipe.c null pointer dereference - CVE-2009-3547
Date: Mon, 22 Nov 2010 12:30:57 -0800 [thread overview]
Message-ID: <4CEAD301.5010203@unix-scripts.com> (raw)
In-Reply-To: <C91073E2.ACDE%keir@xen.org>
On 11/22/2010 11:24 AM, Keir Fraser wrote:
> On 22/11/2010 16:27, "Shaun Reitan"<mailinglists@unix-scripts.com> wrote:
>
>> We've been applying this patch since the fix was discovered but i just
>> realized yesterday when building a new kernel that the Xen kernel does
>> not have this fix applied yet.
>>
>> I also have verified that this exploit works to gain root access on the
>> current http://xenbits.xensource.com/linux-2.6.18-xen.hg branch
>
> It has to be said, very clearly, that our 2.6.18 tree is only really of use
> now as a repository of Xen patches for vendors to pull into their own,
> *properly maintained and secured* kernels. We are very interested in fixing
> Xen-related security issues in our 2.6.18 tree (precisely because others use
> it as a repository of good Xen patches). We are less interested in general
> kernel fixes, although of course as a matter of good form we will consider a
> security fix such as you propose. However, the patch you supplied does not
> apply to the 2.6.18 tree.
>
> Thanks,
> Keir
I see, good to know, thanks!
--
Shaun Retian
Chief Technical Officer
Network Data Center Host, Inc.
http://www.ndchost.com
prev parent reply other threads:[~2010-11-22 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 16:27 [PATCH] fs: pipe.c null pointer dereference - CVE-2009-3547 Shaun Reitan
2010-11-22 19:24 ` Keir Fraser
2010-11-22 20:30 ` Shaun Reitan [this message]
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=4CEAD301.5010203@unix-scripts.com \
--to=mailinglists@unix-scripts.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.