From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] openssl: Version bump. 3.5.3 -> 3.5.4
Date: Fri, 17 Oct 2025 10:20:15 +0200 [thread overview]
Message-ID: <20251017082015.3110191-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251001182658.2042659-1-christian.melki@t2data.com>
Thanks, applied as 6f03d6a0da32770208a722947e794d567511740b.
Michael
[sent from post-receive hook]
On Fri, 17 Oct 2025 10:20:15 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Security patch release.
> https://github.com/openssl/openssl/releases/tag/openssl-3.5.4
>
> Plugs CVEs:
> CVE-2025-9230: Fix Out-of-bounds read & write in RFC 3211 KEK Unwrap.
> CVE-2025-9231: Fix Timing side-channel in SM2 algorithm on 64 bit ARM.
> CVE-2025-9232: Fix Out-of-bounds read in HTTP client no_proxy handling.
>
> * Forward patchset. Applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20251001182658.2042659-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/openssl-3.5.3/0001-debian-targets.patch b/patches/openssl-3.5.4/0001-debian-targets.patch
> similarity index 100%
> rename from patches/openssl-3.5.3/0001-debian-targets.patch
> rename to patches/openssl-3.5.4/0001-debian-targets.patch
> diff --git a/patches/openssl-3.5.3/0002-pic.patch b/patches/openssl-3.5.4/0002-pic.patch
> similarity index 100%
> rename from patches/openssl-3.5.3/0002-pic.patch
> rename to patches/openssl-3.5.4/0002-pic.patch
> diff --git a/patches/openssl-3.5.3/0003-Configure-allow-to-enable-ktls-if-target-does-not-st.patch b/patches/openssl-3.5.4/0003-Configure-allow-to-enable-ktls-if-target-does-not-st.patch
> similarity index 100%
> rename from patches/openssl-3.5.3/0003-Configure-allow-to-enable-ktls-if-target-does-not-st.patch
> rename to patches/openssl-3.5.4/0003-Configure-allow-to-enable-ktls-if-target-does-not-st.patch
> diff --git a/patches/openssl-3.5.3/0004-conf-Serialize-allocation-free-of-ssl_names.patch b/patches/openssl-3.5.4/0004-conf-Serialize-allocation-free-of-ssl_names.patch
> similarity index 100%
> rename from patches/openssl-3.5.3/0004-conf-Serialize-allocation-free-of-ssl_names.patch
> rename to patches/openssl-3.5.4/0004-conf-Serialize-allocation-free-of-ssl_names.patch
> diff --git a/patches/openssl-3.5.3/series b/patches/openssl-3.5.4/series
> similarity index 100%
> rename from patches/openssl-3.5.3/series
> rename to patches/openssl-3.5.4/series
> diff --git a/rules/openssl.make b/rules/openssl.make
> index 0a46f5048532..239a2436ec60 100644
> --- a/rules/openssl.make
> +++ b/rules/openssl.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_OPENSSL) += openssl
> #
> # Paths and names
> #
> -OPENSSL_VERSION := 3.5.3
> -OPENSSL_MD5 := 0ec20faeb96bbb203c8684cc7fe4432e
> +OPENSSL_VERSION := 3.5.4
> +OPENSSL_MD5 := 570a7ab371147b6ba72c6d0fed93131f
> OPENSSL := openssl-$(OPENSSL_VERSION)
> OPENSSL_SUFFIX := tar.gz
> OPENSSL_URL := \
prev parent reply other threads:[~2025-10-17 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 18:26 [ptxdist] [PATCH] " Christian Melki
2025-10-17 8:20 ` 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=20251017082015.3110191-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