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.55 -> 1.6.56
Date: Mon, 13 Apr 2026 09:12:13 +0200 [thread overview]
Message-ID: <20260413071213.342176-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260327213339.90440-1-christian.melki@t2data.com>
Thanks, applied as ef8cdd8317158ba78840aa4949cb7f810d9111fa.
Michael
[sent from post-receive hook]
On Mon, 13 Apr 2026 09:12:13 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Bugfixes and security.
> https://sourceforge.net/p/libpng/code/ci/libpng16/tree/CHANGES
>
> Plugs CVEs:
> CVE-2026-33416: Use-after-free via pointer aliasing in png_set_tRNS and png_set_PLTE
> CVE-2026-33636: Out-of-bounds read/write in the palette expansion on ARM Neon.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260327213339.90440-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 8cdfacf64917..43ad8c8ebaf8 100644
> --- a/rules/libpng.make
> +++ b/rules/libpng.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBPNG) += libpng
> #
> # Paths and names
> #
> -LIBPNG_VERSION := 1.6.55
> -LIBPNG_MD5 := bc950b5a06ec1028285e14a127f6fb6e
> +LIBPNG_VERSION := 1.6.56
> +LIBPNG_MD5 := e30798a97361f11390a624b5b48c1c74
> LIBPNG := libpng-$(LIBPNG_VERSION)
> LIBPNG_SUFFIX := tar.xz
> LIBPNG_URL := $(call ptx/mirror, SF, libpng/$(LIBPNG).$(LIBPNG_SUFFIX))
prev parent reply other threads:[~2026-04-13 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 21:33 [ptxdist] [PATCH] " Christian Melki
2026-04-13 7:12 ` 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=20260413071213.342176-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