From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libjpeg: Version bump. 3.2.0 -> 3.2.1
Date: Fri, 13 Nov 2026 09:39:31 +0100 [thread overview]
Message-ID: <20261113083931.1380763-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261031122359.1518714-1-christian.melki@t2data.com>
Thanks, applied as 21548aa94f4ecdd78f6a48f881277c11249ddfda.
Michael
[sent from post-receive hook]
On Fri, 13 Nov 2026 09:39:31 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Mostly fixes.
> https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/3.2.1
>
> Plugs CVE:
> CVE-2026-75466: integer division-by-zero vulnerability in the PNG loader
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20261031122359.1518714-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libjpeg.make b/rules/libjpeg.make
> index ac06d7ee3fc2..042f07e75bda 100644
> --- a/rules/libjpeg.make
> +++ b/rules/libjpeg.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBJPEG) += libjpeg
> #
> # Paths and names
> #
> -LIBJPEG_VERSION := 3.2.0
> -LIBJPEG_SHA256 := 980dd81f425082aa6d7c9e47fef27554ce7a9ffc8e2f6e863b97d263c5c50858
> +LIBJPEG_VERSION := 3.2.1
> +LIBJPEG_SHA256 := 6f5819c51649bce2571a23b1b0cd41eae2f57fc3f8908c7ec9e7047efb65ca13
> LIBJPEG_SUFFIX := tar.gz
> LIBJPEG := libjpeg-turbo-$(LIBJPEG_VERSION)
> LIBJPEG_URL := https://github.com/libjpeg-turbo/libjpeg-turbo/archive/refs/tags/$(LIBJPEG_VERSION).$(LIBJPEG_SUFFIX)
prev parent reply other threads:[~2026-11-13 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 12:23 [ptxdist] [PATCH] " Christian Melki
2026-11-13 8:39 ` 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=20261113083931.1380763-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