Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Devansh Patel" <devanshp@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH 5/8] curl: fix CVE-2026-8927
Date: Fri, 16 Oct 2026 06:10:23 -0700	[thread overview]
Message-ID: <2040945.1792156223788444481@lists.openembedded.org> (raw)
In-Reply-To: <DM5QFWN94ZTR.1JHKJRMRCI8YA@smile.fr>

[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]

Hi Yoann,

I have rebased the remaining four patches (5/8–8/8) onto stable/scarthgap-review
and Sent v2 [1][2][3][4]. The backport notes now explain the test.h macro requirements,
and the commit messages include the validation results.

The fresh Scarthgap build succeeded along with ptests passing with no failures.

[1] https://lists.openembedded.org/g/openembedded-core/topic/scarthgap_patch_v2_5_8/121787397
[2] https://lists.openembedded.org/g/openembedded-core/topic/scarthgap_patch_v2_6_8/121787401
[3] https://lists.openembedded.org/g/openembedded-core/topic/scarthgap_patch_v2_7_8/121787398
[4] https://lists.openembedded.org/g/openembedded-core/topic/scarthgap_patch_v2_8_8/121787400

Regards,
Devansh

On Fri, Oct 16, 2026 at 03:03 AM, Yoann Congal wrote:

> 
> On Thu Oct 15, 2026 at 10:27 AM CEST, Devansh Patel -X (devanshp - E
> INFOCHIPS PRIVATE LIMITED at Cisco) wrote:
> 
>> Hi Yoann,
> 
> Hello,
> 
> 
>> I compared the submitted backport with upstream. curl 8.7.1 lacks
>> first.h and uses the older test.h harness. Its res_easy_setopt() and
>> res_global_init() macros assign to res, requiring the rename in
>> init1647() and test().
> 
> Ok, now I see it. To give you an idea, this is the kind of info I want
> in the backport notes. Can you send a v2 of the series with that added?
> You will have to rebase on top of stable/scarthgap-review, I took some
> patches of the series.
> 
> 
>> run1647() retains upstream’s result. Following
>> your earlier feedback [1], init1647() also retains the CURLcode type.
>> With those adjustments, the test passes; reversing the library fix
>> reproduces the Digest header leak.
> 
> This info can go into your commit message. Knowing what kind of test was
> done is always good.
> 
> 
>> [1] https://www.mail-archive.com/openembedded-core%40lists.openembedded.org/msg226412.html
>> 
>> Regards,
>> Devansh
> 
> Thanks!
> --
> Yoann Congal
> Smile ECS

[-- Attachment #2: Type: text/html, Size: 2881 bytes --]

  reply	other threads:[~2026-10-16 13:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 11:23 [OE-core][scarthgap][PATCH 1/8] curl: set CVE_STATUS for CVE-2026-9547 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-07 11:23 ` [OE-core][scarthgap][PATCH 2/8] curl: deferred CVE-2026-12064 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-07 11:23 ` [OE-core][scarthgap][PATCH 3/8] curl: fix CVE-2026-8286 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-07 11:23 ` [OE-core][scarthgap][PATCH 4/8] curl: ignore CVE-2026-8924 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-07 11:24 ` [OE-core][scarthgap][PATCH 5/8] curl: fix CVE-2026-8927 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-13 20:10   ` Yoann Congal
2026-10-15  8:27     ` Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-15 21:33       ` Yoann Congal
2026-10-16 13:10         ` Devansh Patel [this message]
2026-10-07 11:24 ` [OE-core][scarthgap][PATCH 6/8] curl: fix CVE-2026-8932 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-07 11:24 ` [OE-core][scarthgap][PATCH 7/8] curl: fix CVE-2026-6429 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-07 11:24 ` [OE-core][scarthgap][PATCH 8/8] curl: fix CVE-2026-7168 Devansh Patel -X (devanshp - 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=2040945.1792156223788444481@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