From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/4] Pull request (cover letter only)
Date: Sat, 23 Jul 2022 05:28:57 -1000 [thread overview]
Message-ID: <cover.1658590082.git.steve@sakoman.com> (raw)
The following changes since commit bba069463ca3813666d084643b0239b9af0199e1:
classes/cve-check: Move get_patches_cves to library (2022-07-13 05:25:10 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Bruce Ashfield (2):
linux-yocto/5.4: update to v5.4.205
linux-yocto-rt/5.4: fixup -rt build breakage
Ranjitsinh Rathod (1):
cve-extra-exclusions.inc: Use CVE_CHECK_WHITELIST
Robert Joslyn (1):
curl: Fix CVE-2022-32206, CVE-2022-32207, and CVE-2022-32208
.../distro/include/cve-extra-exclusions.inc | 6 +-
.../linux/linux-yocto-rt_5.4.bb | 6 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +-
.../curl/curl/CVE-2022-32206.patch | 52 ++++
.../curl/curl/CVE-2022-32207.patch | 284 ++++++++++++++++++
.../curl/curl/CVE-2022-32208.patch | 72 +++++
meta/recipes-support/curl/curl_7.69.1.bb | 3 +
8 files changed, 432 insertions(+), 21 deletions(-)
create mode 100644 meta/recipes-support/curl/curl/CVE-2022-32206.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2022-32207.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2022-32208.patch
--
2.25.1
next reply other threads:[~2022-07-23 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 15:28 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-28 16:15 [OE-core][dunfell 0/4] Pull request (cover letter only) Steve Sakoman
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=cover.1658590082.git.steve@sakoman.com \
--to=steve@sakoman.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