qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: "Samuel Thibault" <samuel.thibault@ens-lyon.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: SLiRP: use-afte-free in ip_reass() [CVE-2020-1983]
Date: Tue, 21 Apr 2020 11:51:14 +0100	[thread overview]
Message-ID: <CAFEAcA81NT6yKndgE_5HqmQYR4OMpkZsLris-bS+Ojw2qoruCA@mail.gmail.com> (raw)
In-Reply-To: <CAJ+F1C+YnbgCkYN1+7zpq0XvZYb2LWL6kbQXRSybJew1JnBgQQ@mail.gmail.com>

On Tue, 21 Apr 2020 at 11:22, Marc-André Lureau
<marcandre.lureau@gmail.com> wrote:
>
> Hi
>
> On Tue, Apr 21, 2020 at 11:18 AM Philippe Mathieu-Daudé
> <philmd@redhat.com> wrote:
> >
> > Hi Samuel and Marc-André,
> >
> > Peter is going to tag 5.0-rc4 (final before release) today.
> > Do you have plans to send a last minute pull-request to fix CVE-2020-1983?
> >
> > https://gitlab.freedesktop.org/slirp/libslirp/-/commit/9ac0371bb
>
> libslirp is not following qemu release schedule.

From the upstream QEMU perspective, this seems to be a bit
of a pain point resulting from the separation of slirp out
into its own module. I do not like being blindsided by
random "oh hey there's a CVE fix but it's in some other
git repository and it's mixed in with a bunch of other
non-critical fixes" news on the day of releasing the
final release candidate :-(

While slirp remains a submodule that is the usual way
that QEMU is built, it would be really helpful if you could
ensure that the submodule works on a release schedule that
works with QEMU rather than against it...

thanks
-- PMM


      parent reply	other threads:[~2020-04-21 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  9:18 SLiRP: use-afte-free in ip_reass() [CVE-2020-1983] Philippe Mathieu-Daudé
2020-04-21 10:22 ` Marc-André Lureau
2020-04-21 10:33   ` Daniel P. Berrangé
2020-04-21 12:56     ` Michael Tokarev
2020-04-21 10:34   ` Philippe Mathieu-Daudé
2020-04-21 10:51   ` Peter Maydell [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=CAFEAcA81NT6yKndgE_5HqmQYR4OMpkZsLris-bS+Ojw2qoruCA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=marcandre.lureau@gmail.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.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).