From: Peter Maydell <peter.maydell@linaro.org>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: "Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH for-5.0?] slirp: update to fix CVE-2020-1983
Date: Wed, 22 Apr 2020 13:47:49 +0100 [thread overview]
Message-ID: <CAFEAcA8Cy4LYO+44bTf82JHtuM13XiSvUhUE-mwbL97kd8Uh_g@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA85GEfDiwo8a9r00x1e6a5d6UDw6LJiYPkm0EstMtccOQ@mail.gmail.com>
On Tue, 21 Apr 2020 at 20:19, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Tue, 21 Apr 2020 at 18:03, Marc-André Lureau
> <marcandre.lureau@redhat.com> wrote:
> >
> > This is an update on the stable-4.2 branch of libslirp.git:
> >
> > git shortlog 55ab21c9a3..2faae0f778f81
> >
> > Marc-André Lureau (1):
> > Fix use-afte-free in ip_reass() (CVE-2020-1983)
> >
> > CVE-2020-1983 is actually a follow up fix for commit
> > 126c04acbabd7ad32c2b018fe10dfac2a3bc1210 ("Fix heap overflow in
> > ip_reass on big packet input") which was was included in qemu
> > v4.1 (commit e1a4a24d262ba5ac74ea1795adb3ab1cd574c7fb "slirp: update
> > with CVE-2019-14378 fix").
> >
> > Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Hi; thanks for putting together this stable-branch update.
> I've run it through my test setup and it's fine; I'm just
> going to wait a little until I push it to master just in case
> anybody wants to speak up with an opinion/objection.
> I'll do that tomorrow afternoon UK time and then tag rc4.
Now applied to master, thanks.
-- PMM
prev parent reply other threads:[~2020-04-22 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 17:02 [PATCH for-5.0?] slirp: update to fix CVE-2020-1983 Marc-André Lureau
2020-04-21 19:19 ` Peter Maydell
2020-04-22 12:47 ` 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=CAFEAcA8Cy4LYO+44bTf82JHtuM13XiSvUhUE-mwbL97kd8Uh_g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=marcandre.lureau@redhat.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).