From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/4] Patch review
Date: Sat, 15 Apr 2023 05:33:35 -1000 [thread overview]
Message-ID: <cover.1681572706.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell and have comments back by
end of day Tuesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5184
The following changes since commit 4045bf02bbc6e87a05ba689a63c675e49c940772:
bmap-tools: switch to main branch (2023-04-03 07:16:26 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut
Bhabu Bindu (1):
ffmpeg: fix for CVE-2022-3341
Gaurav Gupta (1):
qemu: fix build error introduced by CVE-2021-3929 fix
Hitendra Prajapati (2):
ruby: CVE-2023-28756 ReDoS vulnerability in Time
curl: CVE-2023-27534 SFTP path ~ resolving discrepancy
meta/recipes-devtools/qemu/qemu.inc | 2 +
.../qemu/qemu/CVE-2021-3929.patch | 33 ++--
.../hw-block-nvme-handle-dma-errors.patch | 146 ++++++++++++++++++
...w-block-nvme-refactor-nvme_addr_read.patch | 55 +++++++
.../ruby/ruby/CVE-2023-28756.patch | 61 ++++++++
meta/recipes-devtools/ruby/ruby_2.7.6.bb | 1 +
.../ffmpeg/ffmpeg/CVE-2022-3341.patch | 67 ++++++++
.../recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb | 1 +
.../curl/curl/CVE-2023-27534.patch | 123 +++++++++++++++
meta/recipes-support/curl/curl_7.69.1.bb | 1 +
10 files changed, 475 insertions(+), 15 deletions(-)
create mode 100644 meta/recipes-devtools/qemu/qemu/hw-block-nvme-handle-dma-errors.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/hw-block-nvme-refactor-nvme_addr_read.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2023-28756.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2022-3341.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2023-27534.patch
--
2.34.1
next reply other threads:[~2023-04-15 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 15:33 Steve Sakoman [this message]
2023-04-15 15:33 ` [OE-core][dunfell 1/4] ffmpeg: fix for CVE-2022-3341 Steve Sakoman
2023-04-15 15:33 ` [OE-core][dunfell 2/4] qemu: fix build error introduced by CVE-2021-3929 fix Steve Sakoman
2023-04-15 15:33 ` [OE-core][dunfell 3/4] ruby: CVE-2023-28756 ReDoS vulnerability in Time Steve Sakoman
2023-04-15 15:33 ` [OE-core][dunfell 4/4] curl: CVE-2023-27534 SFTP path ~ resolving discrepancy Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2022-07-21 21:38 [OE-core][dunfell 0/4] Patch review Steve Sakoman
2022-05-25 14:36 Steve Sakoman
2021-10-25 23:31 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.1681572706.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