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.50 -> 1.6.51
Date: Thu, 4 Dec 2025 14:14:56 +0100 [thread overview]
Message-ID: <20251204131456.2197549-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251124181514.760559-1-christian.melki@t2data.com>
Thanks, applied as 608d2eff648dc176ef9166d7b6426ea32d0c5f74.
Michael
[sent from post-receive hook]
On Thu, 04 Dec 2025 14:14:56 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Security fixes.
> https://sourceforge.net/p/libpng/code/ci/libpng16/tree/CHANGES
>
> Plugs CVEs:
> CVE-2025-64505: Heap buffer overflow in `png_do_quantize` via malformed palette index.
> CVE-2025-64506: Heap buffer over-read in `png_write_image_8bit` with 8-bit input and `convert_to_8bit` enabled.
> CVE-2025-64720: Buffer overflow in `png_image_read_composite` via incorrect palette premultiplication.
> CVE-2025-65018: Heap buffer overflow in `png_combine_row` triggered via `png_image_finish_read`.
>
> Pretty bad, suggest update.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20251124181514.760559-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 a842038a41d7..86eed1ae5891 100644
> --- a/rules/libpng.make
> +++ b/rules/libpng.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBPNG) += libpng
> #
> # Paths and names
> #
> -LIBPNG_VERSION := 1.6.50
> -LIBPNG_MD5 := e583e61455c4f40d565d85c0e9a2fbf9
> +LIBPNG_VERSION := 1.6.51
> +LIBPNG_MD5 := 8781d5eb8285ac70100b75a1d2a5fc5e
> LIBPNG := libpng-$(LIBPNG_VERSION)
> LIBPNG_SUFFIX := tar.xz
> LIBPNG_URL := $(call ptx/mirror, SF, libpng/$(LIBPNG).$(LIBPNG_SUFFIX))
prev parent reply other threads:[~2025-12-04 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 18:15 [ptxdist] [PATCH] " Christian Melki
2025-12-04 13: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=20251204131456.2197549-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