From: "Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)" <devanshp@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-Core][scarthgap][PATCH 0/4] curl: fix CVE-2026-8927, CVE-2026-8932, CVE-2026-6429 and CVE-2026-7168
Date: Fri, 20 Nov 2026 05:04:10 -0800 [thread overview]
Message-ID: <20261120130414.822854-1-devanshp@cisco.com> (raw)
From: Devansh Patel <devanshp@cisco.com>
This series was developed against the latest OE-Core contrib
stable/scarthgap-review branch.
This series backports fixes for CVE-2026-8927, CVE-2026-8932,
CVE-2026-6429 and CVE-2026-7168 to Scarthgap curl 8.7.1.
The fixes clear Digest state when an environment proxy changes, include
mTLS credentials in connection and session reuse checks, clear redirect
credentials and Digest state across origins, compare IPv6 zone IDs, and
reset proxy authentication when CURLOPT_PROXY changes.
Changes in v3:
- Omit the adapted test additions and minimize differences from upstream.
- Renumber the four curl patches as 1/4 through 4/4.
- Refresh recipe hunks against stable/scarthgap-review.
- Add cross-origin Digest cleanup from upstream 6daf4bc7.
- Compare IPv6 zone IDs in the origin helper using upstream edfc80c7.
- Fold only the required helper prerequisite into
CVE-2026-6429_p1.patch.
- Document target API/header adaptations and omitted test files.
Upstream tests are omitted from the submitted backports. The embedded
patches document omissions and adaptations in Backport Changes and
preserve the original upstream commit messages and public provenance.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
Devansh Patel (4):
curl: Fix CVE-2026-8927
curl: Fix CVE-2026-8932
curl: Fix CVE-2026-6429
curl: Fix CVE-2026-7168
.../curl/curl/CVE-2026-6429_p1.patch | 205 ++++++++++++++++++
.../curl/curl/CVE-2026-6429_p2.patch | 52 +++++
.../curl/curl/CVE-2026-6429_p3.patch | 29 +++
.../curl/curl/CVE-2026-7168.patch | 83 +++++++
.../curl/curl/CVE-2026-8927.patch | 87 ++++++++
.../curl/curl/CVE-2026-8932.patch | 170 +++++++++++++++
meta/recipes-support/curl/curl_8.7.1.bb | 6 +
7 files changed, 632 insertions(+)
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-6429_p1.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-6429_p2.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-6429_p3.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-7168.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-8927.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-8932.patch
next reply other threads:[~2026-11-20 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 13:04 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco) [this message]
2026-11-20 13:04 ` [OE-Core][scarthgap][PATCH 1/4] curl: Fix CVE-2026-8927 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-20 13:04 ` [OE-Core][scarthgap][PATCH 2/4] curl: Fix CVE-2026-8932 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-20 13:04 ` [OE-Core][scarthgap][PATCH 3/4] curl: Fix CVE-2026-6429 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-20 13:04 ` [OE-Core][scarthgap][PATCH 4/4] 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=20261120130414.822854-1-devanshp@cisco.com \
--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