From: "Devansh Patel" <devanshp@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH 1/6] curl: Fix CVE-2026-8286
Date: Wed, 07 Oct 2026 04:39:55 -0700 [thread overview]
Message-ID: <1690975.1791373195261402163@lists.openembedded.org> (raw)
In-Reply-To: <DLICCNG5E097.3K1S7KX9M5QVE@smile.fr>
[-- Attachment #1: Type: text/plain, Size: 3447 bytes --]
Hi Yoann,
Thanks for the review. I regenerated the patches and also adapted few CVE_STATUSES from Wrynose,
sent a new fresh v1 series combining CVEs with Deepak's two fixes for CVE-2026-6429 & CVE-2026-7168 :
New Series: https://patchwork.yoctoproject.org/project/oe-core/list/?series=51870
The series applies to Scarthgap and curl 8.7.1. Please consider my earlier six-patch series superseded.
Regards,
Devansh
On Fri, Sep 18, 2026 at 03:10 PM, Yoann Congal wrote:
>
> On Fri Sep 4, 2026 at 11:00 AM CEST, Devansh Patel via
> lists.openembedded.org wrote:
>
>> From: Devansh Patel <devanshp@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/a86efdd7ca5433de9231e650f18247de8319ad16
>>
>> [2] https://curl.se/docs/CVE-2026-8286.html
>>
>> Signed-off-by: Devansh Patel <devanshp@cisco.com>
>> ---
>> .../curl/curl/CVE-2026-8286.patch | 60 +++++++++++++++++++
>> meta/recipes-support/curl/curl_8.7.1.bb | 1 +
>> 2 files changed, 61 insertions(+)
>> create mode 100644 meta/recipes-support/curl/curl/CVE-2026-8286.patch
>>
>> diff --git a/meta/recipes-support/curl/curl/CVE-2026-8286.patch
>> b/meta/recipes-support/curl/curl/CVE-2026-8286.patch
>> new file mode 100644
>> index 0000000000..ec2f6165c3
>> --- /dev/null
>> +++ b/meta/recipes-support/curl/curl/CVE-2026-8286.patch
>> @@ -0,0 +1,60 @@
>> +From 471592386ff977dfd3e2de107b8f81dfc1d3d030 Mon Sep 17 00:00:00 2001
>> +From: Stefan Eissing <stefan@eissing.org>
>> +Date: Thu, 7 May 2026 10:30:07 +0200
>> +Subject: [PATCH] url: fix connection reuse for starttls protocols
>> +
>> +When a connection is tested for reuse in a transfer that *may* upgrade
>> +to TLS (commonly via STARTTLS), the SSL configuration must match the
>> +existing connection.
>> +
>> +Reported-by: Andrew Nesbit
>> +Closes #21522
>> +
>> +CVE: CVE-2026-8286
>> +Upstream-Status: Backport [ https://github.com/curl/curl/commit/a86efdd7ca5433de9231e650f18247de8319ad16
>> ]
>> +
>> +Backport Changes:
>> +- curl 8.7.1 predates the url_conn_match refactor. Carry the upstream
>> may-TLS
>> + and require-TLS distinction in ConnectionExists() and preserve the
>> upstream
>> + TLS configuration matching behavior.
>> +
>> +(cherry picked from commit a86efdd7ca5433de9231e650f18247de8319ad16)
>> +Signed-off-by: Devansh Patel <devanshp@cisco.com>
>> +---
>> + lib/url.c | 9 +++++----
>> + 1 file changed, 5 insertions(+), 4 deletions(-)
>> +
>
> Hello,
>
> This patch and the other ones in the series have formating issues:
>
>
>> +diff --git a/lib/url.c b/lib/url.c
>> +index dfcd6f4841..9e1ca0336c 100644
>> +--- a/lib/url.c
>> ++++ b/lib/url.c
>> +@@ -935,7 +935,8 @@ ConnectionExists(struct Curl_easy *data,
>> + /* plain HTTP with upgrade */
>> + bool h2upgrade = (data->state.httpwant == CURL_HTTP_VERSION_2_0) &&
>> + (needle->handler->protocol & CURLPROTO_HTTP);
>> +- bool req_tls = data->set.use_ssl >= CURLUSESSL_CONTROL;
>> ++ bool require_tls = data->set.use_ssl >= CURLUSESSL_CONTROL;
>> ++ bool may_tls = data->set.use_ssl > CURLUSESSL_NONE;
>> +
>
> ^ For exemple, here it lacks a space to mark context.
>
> If you use interdiff to compare the upstream patch and yours, it is
> quite noticeable.
>
> Can you send a v2 with those fixed?
>
> Thanks!
> --
> Yoann Congal
> Smile ECS
[-- Attachment #2: Type: text/html, Size: 4028 bytes --]
prev parent reply other threads:[~2026-10-07 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 9:00 [OE-core][scarthgap][PATCH 1/6] curl: Fix CVE-2026-8286 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-09-04 9:00 ` [OE-core][scarthgap][PATCH 2/6] curl: Fix CVE-2026-8924 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-09-04 9:00 ` [OE-core][scarthgap][PATCH 3/6] curl: Fix CVE-2026-8927 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-09-04 9:00 ` [OE-core][scarthgap][PATCH 4/6] curl: Fix CVE-2026-8932 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-09-04 9:00 ` [OE-core][scarthgap][PATCH 5/6] curl: Fix CVE-2026-9547 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-09-04 9:00 ` [OE-core][scarthgap][PATCH 6/6] curl: Fix CVE-2026-12064 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-09-18 9:40 ` [OE-core][scarthgap][PATCH 1/6] curl: Fix CVE-2026-8286 Yoann Congal
2026-10-07 11:39 ` Devansh Patel [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=1690975.1791373195261402163@lists.openembedded.org \
--to=devanshp@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;
as well as URLs for NNTP newsgroup(s).