mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] zlib: Version bump. 1.3.2 -> 1.4
Date: Tue, 17 Nov 2026 07:14:38 +0100	[thread overview]
Message-ID: <20261117061438.3091361-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261106212810.3985300-1-christian.melki@t2data.com>

Thanks, applied as 8c40f6b993b318a0c6cf28583426c72c50d8c5e4.

Michael

[sent from post-receive hook]

On Tue, 17 Nov 2026 07:14:38 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> A bunch of security fixes of various tracking origin including CVEs.
> https://github.com/madler/zlib/releases/tag/v1.4
> 
> Plugs CVEs:
> CVE-2026-85091: gzwrite() buffer overflow
> CVE-2026-4738: inftree out-of-bounds pointer arithmetic
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20261106212810.3985300-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/zlib.make b/rules/zlib.make
> index 0960b0f65b1b..2e4ad8715112 100644
> --- a/rules/zlib.make
> +++ b/rules/zlib.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_ZLIB) += zlib
>  # Paths and names
>  #
>  
> -ZLIB_VERSION	:= 1.3.2
> -ZLIB_SHA256	:= d7a0654783a4da529d1bb793b7ad9c3318020af77667bcae35f95d0e42a792f3
> +ZLIB_VERSION	:= 1.4
> +ZLIB_SHA256	:= 4f11c512053d7bab8d9e9b89bde3575add3e4c50a383b42ef6cb837035fc5a7c
>  ZLIB		:= zlib-$(ZLIB_VERSION)
>  ZLIB_SUFFIX	:= tar.xz
>  ZLIB_URL	:= \



      reply	other threads:[~2026-11-17  6:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 21:28 [ptxdist] [PATCH] " Christian Melki
2026-11-17  6:14 ` Michael Olbrich [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=20261117061438.3091361-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /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