From: "Yoann Congal" <yoann.congal@smile.fr>
To: <dkelaiya@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][wrynose][PATCH 4/5] curl: fix CVE-2026-82208
Date: Tue, 20 Oct 2026 16:15:15 +0200 [thread overview]
Message-ID: <DM9Q8TS5ICO7.1APSVWR4YLU7R@smile.fr> (raw)
In-Reply-To: <20261019064320.3978613-5-dkelaiya@cisco.com>
On Mon Oct 19, 2026 at 8:43 AM CEST, Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> From: Darsh Kelaiya <dkelaiya@cisco.com>
>
> This patch applies the upstream fix as referenced in [2],
> using the commit shown in [1].
>
> [1] https://github.com/curl/curl/commit/ed0338befd1d865a8ea1fbaa90013a096dedd07a
> [2] https://curl.se/docs/CVE-2026-82208.html
>
> Signed-off-by: Darsh Kelaiya <dkelaiya@cisco.com>
> ---
> .../curl/curl/CVE-2026-82208.patch | 52 +++++++++++++++++++
> meta/recipes-support/curl/curl_8.19.0.bb | 1 +
> 2 files changed, 53 insertions(+)
> create mode 100644 meta/recipes-support/curl/curl/CVE-2026-82208.patch
>
> diff --git a/meta/recipes-support/curl/curl/CVE-2026-82208.patch b/meta/recipes-support/curl/curl/CVE-2026-82208.patch
> new file mode 100644
> index 0000000000..2c733de210
> --- /dev/null
> +++ b/meta/recipes-support/curl/curl/CVE-2026-82208.patch
> @@ -0,0 +1,52 @@
> +From ed0338befd1d865a8ea1fbaa90013a096dedd07a Mon Sep 17 00:00:00 2001
> +From: Stefan Eissing <stefan@eissing.org>
> +Date: Wed, 26 Aug 2026 13:46:13 +0200
> +Subject: [PATCH] wolfssl: do not run Curl_wssl_setup_x509_store() twice
> +
> +The flag preventing a rerun was not set when a cached_store
> +was used.
> +
> +CURL_UNCONST an ech string for my old wolfssl version
> +
> +Closes #22689
> +
> +CVE: CVE-2026-82208
> +Upstream-Status: Backport [https://github.com/curl/curl/commit/ed0338befd1d865a8ea1fbaa90013a096dedd07a]
> +
> +Backport Changes:
> +- Omitted the unrelated CURL_UNCONST ECH compatibility change because
> + curl 8.19.0 uses a mutable ECH configuration string and a different
> + code path.
Can you justify this? How can I know that difference from upstream just
broke ECH or introduced a vulnerability?
Regards,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-10-20 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 6:43 [OE-core][wrynose][PATCH 0/5] curl: backport security fixes Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-19 6:43 ` [OE-core][wrynose][PATCH 1/5] curl: fix CVE-2026-8926 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-20 13:43 ` Yoann Congal
2026-10-19 6:43 ` [OE-core][wrynose][PATCH 2/5] curl: fix CVE-2026-11564 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-20 13:53 ` Yoann Congal
2026-10-19 6:43 ` [OE-core][wrynose][PATCH 3/5] curl: fix CVE-2026-80255 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-20 14:12 ` Yoann Congal
2026-10-19 6:43 ` [OE-core][wrynose][PATCH 4/5] curl: fix CVE-2026-82208 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-20 14:15 ` Yoann Congal [this message]
2026-10-19 6:43 ` [OE-core][wrynose][PATCH 5/5] curl: fix CVE-2026-80231 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
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=DM9Q8TS5ICO7.1APSVWR4YLU7R@smile.fr \
--to=yoann.congal@smile.fr \
--cc=dkelaiya@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
/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