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.53 -> 1.6.54
Date: Fri, 23 Jan 2026 16:02:08 +0100 [thread overview]
Message-ID: <20260123150208.1572491-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260115201203.1824095-1-christian.melki@t2data.com>
Thanks, applied as 94c0f1589817c397dc57e6bcaa097c0766d20ad8.
Michael
[sent from post-receive hook]
On Fri, 23 Jan 2026 16:02:08 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Security fixes.
> https://sourceforge.net/p/libpng/code/ci/libpng16/tree/CHANGES
>
> Plugs CVEs:
> CVE-2026-22695: Heap buffer over-read in png_image_read_direct_scaled.
> CVE-2026-22801: Integer truncation causing heap buffer over-read in png_image_write_*
>
> * License hash changed, copyright year updates.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260115201203.1824095-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 7bd6d2376c1b..f69de3e081f5 100644
> --- a/rules/libpng.make
> +++ b/rules/libpng.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBPNG) += libpng
> #
> # Paths and names
> #
> -LIBPNG_VERSION := 1.6.53
> -LIBPNG_MD5 := 0d95e8af31991e976811bbf55f693d2d
> +LIBPNG_VERSION := 1.6.54
> +LIBPNG_MD5 := ba9e86853c794d111398b66a42bfa0dc
> LIBPNG := libpng-$(LIBPNG_VERSION)
> LIBPNG_SUFFIX := tar.xz
> LIBPNG_URL := $(call ptx/mirror, SF, libpng/$(LIBPNG).$(LIBPNG_SUFFIX))
> @@ -25,7 +25,7 @@ LIBPNG_SOURCE := $(SRCDIR)/$(LIBPNG).$(LIBPNG_SUFFIX)
> LIBPNG_DIR := $(BUILDDIR)/$(LIBPNG)
> LIBPNG_LICENSE := libpng-2.0
> LIBPNG_LICENSE_FILES := \
> - file://LICENSE;md5=5516d77a3cf75f55a0d37254e3e65a20
> + file://LICENSE;md5=9dc350edbbbee660c7d9af79487168f2
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2026-01-23 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 20:12 [ptxdist] [PATCH] " Christian Melki
2026-01-23 15:02 ` 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=20260123150208.1572491-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