Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Bastien Jauny" <bastien.jauny@smile.fr>
To: <dkelaiya@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap][PATCH 3/3] curl: set CVE_STATUS for CVE-2026-80231
Date: Wed, 18 Nov 2026 11:54:17 +0100	[thread overview]
Message-ID: <DMYA4R46NAH8.35CZD2IV2F2X9@smile.fr> (raw)
In-Reply-To: <20261104105645.2523473-4-dkelaiya@cisco.com>

On Wed Nov 4, 2026 at 11:56 AM CET, Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco) via openembedded-core wrote:
> From: Darsh Kelaiya <dkelaiya@cisco.com>
>
> Analysis:
> - Select the native CA connection-reuse fix in [2], identified by
>   the advisory [1]. It compares the effective native CA setting.
> - The advisory limits the issue to Windows and macOS [1]. Scarthgap
>   builds curl, curl-native and nativesdk-curl for Linux.
> - In curl 8.7.1, native_ca_store is derived from CURLSSLOPT_NATIVE_CA.
>   The same flag is retained in ssl_primary_config.ssl_options,
>   which is cloned and compared for connection reuse.
> - The later implicit native CA selection in [3] is absent from the
>   Scarthgap source. Do not import the Wrynose TLS configuration patch.
> - Hence ignoring the CVE using not-applicable-platform for Linux.
>   Reassess if the SDK platform or native CA configuration changes.
>
> Reference:
> [1] https://curl.se/docs/CVE-2026-80231.html
> [2] https://github.com/curl/curl/commit/7be1e70cb6bcd83e130ecfe8cb91b6a7dcdeff42
> [3] https://github.com/curl/curl/commit/eefd03c572996e5de4dec4fe295ad6f103e0eefc
>
> Signed-off-by: Darsh Kelaiya <dkelaiya@cisco.com>
> ---
>  meta/recipes-support/curl/curl_8.7.1.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-support/curl/curl_8.7.1.bb b/meta/recipes-support/curl/curl_8.7.1.bb
> index 33265f0f25..28d834abb2 100644
> --- a/meta/recipes-support/curl/curl_8.7.1.bb
> +++ b/meta/recipes-support/curl/curl_8.7.1.bb
> @@ -66,6 +66,7 @@ CVE_STATUS[CVE-2026-9547] = "not-applicable-config: vulnerable libssh backend is
>  CVE_STATUS[CVE-2026-82209] = "not-applicable-config: public suffix list support is disabled by the recipe with --without-libpsl"
>  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-19931] = "${@bb.utils.contains('PACKAGECONFIG', 'krb5 negotiate-auth', 'unpatched', 'not-applicable-config: GSS-API Negotiate is disabled', d)}"
> +CVE_STATUS[CVE-2026-80231] = "not-applicable-platform: native CA reuse issue affects Windows and macOS, not Linux"
>  
>  inherit autotools pkgconfig binconfig multilib_header ptest
>  

Hi Darsh,

This will need to be addressed upstream first. I see that this CVE is
already discussed in wrynose so we'll put this patch on hold for now.

Thanks,
-- 
Bastien Jauny
Smile


      reply	other threads:[~2026-11-18 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 10:56 [OE-core][scarthgap][PATCH 0/3] curl: Security fixes Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-04 10:56 ` [OE-core][scarthgap][PATCH 1/3] curl: set CVE_STATUS for CVE-2026-19931 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-04 10:56 ` [OE-core][scarthgap][PATCH 2/3] curl: fix CVE-2026-18924 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-04 10:56 ` [OE-core][scarthgap][PATCH 3/3] curl: set CVE_STATUS for CVE-2026-80231 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-18 10:54   ` Bastien Jauny [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=DMYA4R46NAH8.35CZD2IV2F2X9@smile.fr \
    --to=bastien.jauny@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