From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 0/5] Patch review
Date: Tue, 9 Sep 2025 12:29:58 -0700 [thread overview]
Message-ID: <cover.1757446071.git.steve@sakoman.com> (raw)
Please review this set of changes for kirkstone and have comments back by
end of day Thursday, September 11
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2346
The following changes since commit 71ed9d8394f7e625270ee66f9c2816bba4aa2016:
pulseaudio: Add audio group explicitly (2025-09-02 09:20:07 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
Archana Polampalli (3):
ffmpeg: fix CVE-2025-7700
ffmpeg: fix multiple CVEs
ffmpeg: fix CVE-2025-1594
Divya Chellam (1):
wpa-supplicant: fix CVE-2022-37660
Gyorgy Sarvari (1):
llvm: fix typo in CVE-2024-0151.patch
.../wpa-supplicant/CVE-2022-37660-0001.patch | 254 +++++
.../wpa-supplicant/CVE-2022-37660-0002.patch | 139 +++
.../wpa-supplicant/CVE-2022-37660-0003.patch | 196 ++++
.../wpa-supplicant/CVE-2022-37660-0004.patch | 941 ++++++++++++++++++
.../wpa-supplicant/CVE-2022-37660-0005.patch | 144 +++
.../wpa-supplicant/wpa-supplicant_2.10.bb | 5 +
.../llvm/llvm/CVE-2024-0151.patch | 13 +-
...602-CVE-2023-6604-CVE-2023-6605-0001.patch | 79 ++
...602-CVE-2023-6604-CVE-2023-6605-0002.patch | 142 +++
...602-CVE-2023-6604-CVE-2023-6605-0003.patch | 45 +
.../ffmpeg/ffmpeg/CVE-2025-1594.patch | 104 ++
.../ffmpeg/ffmpeg/CVE-2025-7700.patch | 52 +
.../recipes-multimedia/ffmpeg/ffmpeg_5.0.3.bb | 5 +
13 files changed, 2114 insertions(+), 5 deletions(-)
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/CVE-2022-37660-0001.patch
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/CVE-2022-37660-0002.patch
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/CVE-2022-37660-0003.patch
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/CVE-2022-37660-0004.patch
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/CVE-2022-37660-0005.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2023-6602-CVE-2023-6604-CVE-2023-6605-0001.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2023-6602-CVE-2023-6604-CVE-2023-6605-0002.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2023-6602-CVE-2023-6604-CVE-2023-6605-0003.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2025-1594.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2025-7700.patch
--
2.43.0
next reply other threads:[~2025-09-09 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 19:29 Steve Sakoman [this message]
2025-09-09 19:29 ` [OE-core][kirkstone 1/5] ffmpeg: fix CVE-2025-7700 Steve Sakoman
2025-09-09 19:30 ` [OE-core][kirkstone 2/5] ffmpeg: fix multiple CVEs Steve Sakoman
2025-09-09 19:30 ` [OE-core][kirkstone 3/5] ffmpeg: fix CVE-2025-1594 Steve Sakoman
2025-09-09 19:30 ` [OE-core][kirkstone 4/5] llvm: fix typo in CVE-2024-0151.patch Steve Sakoman
2025-09-09 19:30 ` [OE-core][kirkstone 5/5] wpa-supplicant: fix CVE-2022-37660 Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-11-06 13:33 [OE-core][kirkstone 0/5] Patch review Steve Sakoman
2024-10-17 13:31 Steve Sakoman
2024-10-09 16:16 Steve Sakoman
2024-07-31 12:02 Steve Sakoman
2024-04-29 12:53 Steve Sakoman
2023-12-12 22:40 Steve Sakoman
2022-09-14 19:10 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.1757446071.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.