From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libpng: Version bump. 1.6.54 -> 1.6.55
Date: Mon, 2 Mar 2026 10:25:21 +0100 [thread overview]
Message-ID: <20260302092521.3502393-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260213181827.1384662-1-christian.melki@t2data.com>
Thanks, applied as d2cdae5005a46a795b3e9f4d510c4262e4b9bdef.
Michael
[sent from post-receive hook]
On Mon, 02 Mar 2026 10:25:21 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> High severity security fix.
> https://sourceforge.net/p/libpng/code/ci/libpng16/tree/CHANGES
>
> Plugs CVE:
> CVE-2026-25646: Heap buffer overflow in png_set_quantize.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260213181827.1384662-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libpng.make b/rules/libpng.make
> index f69de3e081f5..8cdfacf64917 100644
> --- a/rules/libpng.make
> +++ b/rules/libpng.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBPNG) += libpng
> #
> # Paths and names
> #
> -LIBPNG_VERSION := 1.6.54
> -LIBPNG_MD5 := ba9e86853c794d111398b66a42bfa0dc
> +LIBPNG_VERSION := 1.6.55
> +LIBPNG_MD5 := bc950b5a06ec1028285e14a127f6fb6e
> LIBPNG := libpng-$(LIBPNG_VERSION)
> LIBPNG_SUFFIX := tar.xz
> LIBPNG_URL := $(call ptx/mirror, SF, libpng/$(LIBPNG).$(LIBPNG_SUFFIX))
prev parent reply other threads:[~2026-03-02 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 18:18 [ptxdist] [PATCH] " Christian Melki
2026-03-02 9:25 ` 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=20260302092521.3502393-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