From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Mauro Matteo Cascella <mcascell@redhat.com>,
<oss-security@lists.openwall.com>
Cc: <xen-announce@lists.xen.org>, <xen-devel@lists.xen.org>,
<xen-users@lists.xen.org>,
Xen.org security team <security-team-members@xen.org>
Subject: Re: [oss-security] Xen Security Advisory 355 v2 - stack corruption from XSA-346 change
Date: Mon, 30 Nov 2020 16:10:35 +0000 [thread overview]
Message-ID: <10f61e14-05f3-0294-8cda-e63764d98cbc@citrix.com> (raw)
In-Reply-To: <CAA8xKjWY2+xo57n8hsvG6yMyhs6nAH+S4NbCsEJLWEVff_aWzg@mail.gmail.com>
On 30/11/2020 16:07, Mauro Matteo Cascella wrote:
> Hello,
>
> Has a CVE been assigned for this issue?
>
> Regards,
Some unknown 3rd party appears to have allocated a CVE and we're
currently trying to track down who.
~Andrew
prev parent reply other threads:[~2020-11-30 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 12:03 Xen Security Advisory 355 v2 - stack corruption from XSA-346 change Xen.org security team
2020-11-30 16:07 ` [oss-security] " Mauro Matteo Cascella
2020-11-30 16:10 ` Andrew Cooper [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=10f61e14-05f3-0294-8cda-e63764d98cbc@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=mcascell@redhat.com \
--cc=oss-security@lists.openwall.com \
--cc=security-team-members@xen.org \
--cc=xen-announce@lists.xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xen.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).