From: Nick Clifton <nickc@redhat.com>
To: Luis Machado <luis.machado@arm.com>,
binutils@sourceware.org,
"gdb@sourceware.org" <gdb@sourceware.org>,
gcc@gcc.gnu.org
Subject: Re: [CVE] zlib (< 1.2.12) memory corruption
Date: Fri, 8 Apr 2022 14:36:52 +0100 [thread overview]
Message-ID: <3a271c96-047b-1cd3-54c9-e103421602d3@redhat.com> (raw)
In-Reply-To: <aeecafc4-da37-240f-8f3e-ca2ca58f364f@arm.com>
Hi Luis,
> There is a CVE [1] for zlib < 1.2.12 (released march 27th).
>
> GCC currently uses zlib 1.2.11, and binutils-gdb imports the zlib directory from GCC. The recommendation is to get it updated to 1.2.12, which contains the proper fix [2].
I am all for updating the binutils-gdb copy of zlib. I will wait a couple of
days to see if anyone else has any comments or concerns, but if not, then I
will apply the patches myself.
Cheers
Nick
next prev parent reply other threads:[~2022-04-08 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 13:56 Luis Machado
2022-04-08 13:36 ` Nick Clifton [this message]
2022-04-12 7:30 ` Luis Machado
2022-04-12 15:27 ` Nick Clifton
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=3a271c96-047b-1cd3-54c9-e103421602d3@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).