From: "Yoann Congal" <yoann.congal@smile.fr>
To: <sdoshi@mvista.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][wrynose][PATCH 5/6] curl: set CVE_STATUS for CVE-2026-82208
Date: Wed, 16 Sep 2026 23:43:58 +0200 [thread overview]
Message-ID: <DLH2HV018OZJ.26NTHUR16MZSH@smile.fr> (raw)
In-Reply-To: <20260909203324.765094-5-sdoshi@mvista.com>
On Wed Sep 9, 2026 at 10:33 PM CEST, Siddharth Doshi via lists.openembedded.org wrote:
> From: Siddharth Doshi <sdoshi@mvista.com>
>
> Analysis:
> - The problem only exists when curl is built to use the wolfSSL TLS backend.[1]
> - The recipe is built with OpenSSL and not wolfSSL.
> - Hence, ignoring the CVE for this recipe.
>
> Reference:
> [1] https://curl.se/docs/CVE-2026-82208.html
>
> Signed-off-by: Siddharth Doshi <sdoshi@mvista.com>
> ---
> meta/recipes-support/curl/curl_8.19.0.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-support/curl/curl_8.19.0.bb b/meta/recipes-support/curl/curl_8.19.0.bb
> index a5606c5eb1..68baac1a15 100644
> --- a/meta/recipes-support/curl/curl_8.19.0.bb
> +++ b/meta/recipes-support/curl/curl_8.19.0.bb
> @@ -46,6 +46,7 @@ CVE_STATUS[CVE-2026-8924] = "not-applicable-config: public suffix list support i
> CVE_STATUS[CVE-2026-10536] = "${@bb.utils.contains('PACKAGECONFIG', 'nghttp2', 'unpatched', 'not-applicable-config: applicable only with HTTP/2', d)}"
> CVE_STATUS[CVE-2026-9547] = "not-applicable-config: vulnerable libssh backend is not enabled by the recipe"
> CVE_STATUS[CVE-2026-12064] = "${@bb.utils.contains('PACKAGECONFIG', 'libssh2', 'unpatched', 'not-applicable-config: SCP/SFTP support is not enabled in PACKAGECONFIG', d)}"
> +CVE_STATUS[CVE-2026-82208] = "not-applicable-config: vulnerable wolfSSL backend is not enabled by the recipe"
>
> inherit autotools pkgconfig binconfig multilib_header ptest
>
Hello,
We can't do that, as there are users of the wolfssl backend in the OE
ecosystem: https://github.com/wolfSSL/meta-wolfssl/blob/master/recipes-support/curl/curl_%25.bbappend
The fix does not seem very complex, can we backport it instead?
https://github.com/curl/curl/commit/ed0338befd1d865a8ea1fbaa90
Maybe CC meta-wolfssl maintainers on the patch so that they are
aware/have a chance to review/test it.
Thanks!
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-09-16 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 20:33 [OE-core][wrynose][PATCH 1/6] curl: Security Fix for CVE-2026-13608 Siddharth
2026-09-09 20:33 ` [OE-core][wrynose][PATCH 2/6] curl: Security Fix for CVE-2026-18924 Siddharth
2026-09-27 6:35 ` Yoann Congal
2026-09-09 20:33 ` [OE-core][wrynose][PATCH 3/6] curl: Security Fix for CVE-2026-80229 Siddharth
2026-09-09 20:33 ` [OE-core][wrynose][PATCH 4/6] curl: Security Fix for CVE-2026-80255 Siddharth
2026-09-16 12:17 ` Yoann Congal
2026-09-17 5:06 ` [wrynose][PATCH " Siddharth Doshi
2026-09-09 20:33 ` [OE-core][wrynose][PATCH 5/6] curl: set CVE_STATUS for CVE-2026-82208 Siddharth
2026-09-16 21:43 ` Yoann Congal [this message]
2026-09-17 4:55 ` [wrynose][PATCH " Siddharth Doshi
2026-09-09 20:33 ` [OE-core][wrynose][PATCH 6/6] curl: set CVE_STATUS for CVE-2026-82209 Siddharth
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=DLH2HV018OZJ.26NTHUR16MZSH@smile.fr \
--to=yoann.congal@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=sdoshi@mvista.com \
/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