From: Prasanth R <ragaprasanth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: paul@pbarker.dev, peter.marko@siemens.com,
Prasanth R <ragaprasanth@gmail.com>
Subject: [PATCH v2 1/2] zlib: upgrade 1.3.2 -> 1.4
Date: Fri, 6 Nov 2026 10:13:23 +0900 [thread overview]
Message-ID: <20261106011324.626292-1-ragaprasanth@gmail.com> (raw)
Bug fix and security release. It fixes CVE-2026-85091, a heap buffer
overflow in gzwrite(), and several inflate, deflate and gzread issues.
Drop the -fuse-ld=bfd workaround. 1.4 fixes the configure test that
failed with lld 17+ (upstream commit 6ddc2d0, "Fix configure when using
zlib.map with some linkers"). PR #936, named in the old comment, is
about --zprefix builds, which we don't use.
License checksum is unchanged.
Changelog: https://github.com/madler/zlib/blob/v1.4/ChangeLog
AI-Generated: Uses Claude
Signed-off-by: Prasanth R <prasanth.r@lineo.co.jp>
---
Notes:
v2: zlib 1.4 is out, so upgrade instead of the backport (Peter), and
mark CVE-2026-76844 cpe-incorrect in a separate patch (Paul).
Also drop the lld workaround: tested a 1.4 build with gcc + ld.lld,
same exported symbols as with bfd. ptest passes on Test.
meta/recipes-core/zlib/{zlib_1.3.2.bb => zlib_1.4.bb} | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
rename meta/recipes-core/zlib/{zlib_1.3.2.bb => zlib_1.4.bb} (85%)
diff --git a/meta/recipes-core/zlib/zlib_1.3.2.bb b/meta/recipes-core/zlib/zlib_1.4.bb
similarity index 85%
rename from meta/recipes-core/zlib/zlib_1.3.2.bb
rename to meta/recipes-core/zlib/zlib_1.4.bb
index 8a23d98cd3..18b27df878 100644
--- a/meta/recipes-core/zlib/zlib_1.3.2.bb
+++ b/meta/recipes-core/zlib/zlib_1.4.bb
@@ -12,16 +12,13 @@ SRC_URI = "https://zlib.net/${BP}.tar.gz \
"
UPSTREAM_CHECK_URI = "http://zlib.net/"
-SRC_URI[sha256sum] = "bb329a0a2cd0274d05519d61c667c062e06990d72e125ee2dfa8de64f0119d16"
+SRC_URI[sha256sum] = "02dd159783677a749c04adbdd02b55b8a2bcc7e054f51b76b549199a916ad584"
# When a new release is made the previous release is moved to fossils/, so add this
# to PREMIRRORS so it is also searched automatically.
PREMIRRORS:append = " https://zlib.net/ https://zlib.net/fossils/"
CFLAGS += "-D_REENTRANT -fPIE"
-# zlib does not build with lld, keep it until https://github.com/madler/zlib/pull/936
-# is addressed
-LDFLAGS:append = " -fuse-ld=bfd"
RDEPENDS:${PN}-ptest += "make"
--
2.34.1
next reply other threads:[~2026-11-06 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:13 Prasanth R [this message]
2026-11-06 1:13 ` [PATCH v2 2/2] zlib: ignore CVE-2026-76844 Prasanth R
2026-11-06 6:53 ` Marko, Peter
2026-11-06 8:13 ` Prasanth Ramesh
2026-11-06 8:28 ` Prasanth Ramesh
2026-11-06 9:21 ` Paul Barker
2026-11-06 9:22 ` Prasanth Ramesh
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=20261106011324.626292-1-ragaprasanth@gmail.com \
--to=ragaprasanth@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
--cc=peter.marko@siemens.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