From: "Daniel P. Berrangé" <berrange@redhat.com>
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>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: SLiRP: use-afte-free in ip_reass() [CVE-2020-1983]
Date: Tue, 21 Apr 2020 11:33:07 +0100 [thread overview]
Message-ID: <20200421103307.GB479771@redhat.com> (raw)
In-Reply-To: <CAJ+F1C+YnbgCkYN1+7zpq0XvZYb2LWL6kbQXRSybJew1JnBgQQ@mail.gmail.com>
On Tue, Apr 21, 2020 at 12:22:05PM +0200, Marc-André Lureau 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. The master branch has
> a few changes that shouldn't be added to the release. We could create
> version/stable/qemu branches, but then between each version, we would
> end up with the submodule jumping between branches (with a non-linear
> history). Is that the only option?
In the short term, it looks like a stable branch is the easiest option.
In the medium term, we need to more strongly push people to use the
distro provided slirp, or build it themselves, like they would have to
for (almost) any other 3rd party library we depend on. QEMU shouldn't
carry on doing the work of OS vendors indefinitely for slirp by having
to worry about updates to pull in CVE fixes from an external project.
I've got a few configure patches nearly ready to send to add such a
deprecation. It's been a year since QEMU switched Slirp to be a
submodule, and even longer since Slirp started as an independant
project. With some time allowed for the deprecation period, it will
be nearly 2 years before we finally remove Slirp from QEMU entirely.
Admittedly this may be troublesome for Debian which, AFAICT, does not
add new packages to pre-existing stable releases. Presumably someone
can add it to the "backports" release archive if this is too hard to
get into a stable release ? Failing that, users would have to build
slirp themselves.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-04-21 10:34 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é [this message]
2020-04-21 12:56 ` Michael Tokarev
2020-04-21 10:34 ` Philippe Mathieu-Daudé
2020-04-21 10:51 ` Peter Maydell
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=20200421103307.GB479771@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=peter.maydell@linaro.org \
--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).