From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 00/17] Pull request (cover letter only)
Date: Fri, 17 Sep 2021 23:46:27 +0800 [thread overview]
Message-ID: <cover.1631893475.git.anuj.mittal@intel.com> (raw)
Please merge these changes.
Thanks,
Anuj
The following changes since commit 567dd35d893c5d8969d41f263a24da8fbae3fc2f:
build-appliance-image: Update to hardknott head revision (2021-09-09 10:19:49 +0100)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/hardknott-next
Armin Kuster (1):
apr: Security fix for CVE-2021-35940
Bruce Ashfield (4):
linux-yocto/5.10: update to v5.10.61
linux-yocto/5.10: update to v5.10.63
linux-yocto/5.4: update to v5.4.143
linux-yocto/5.4: update to v5.4.144
Changqing Li (1):
sqlite3: fix CVE-2021-36690
Kai Kang (2):
mc: fix CVE-2021-36370
squashfs-tools: fix CVE-2021-40153
Kiran Surendran (2):
ffmpeg: fix CVE-2021-38291
ffmpeg: fix CVE-2021-38171
Mingli Yu (1):
ruby: fix CVE-2021-31799
Richard Purdie (4):
tcl: Exclude CVE-2021-35331 from checks
flex: Add CVE-2019-6293 to exclusions for checks
go: Exclude CVE-2021-29923 from report list
systemtap: Fix headers issue with x86 and 5.13 headers
Trevor Gamblin (1):
bluez5: fix CVE-2021-0129
Yi Zhao (1):
ruby: Security fixes for CVE-2021-31810/CVE-2021-32066
meta/recipes-connectivity/bluez5/bluez5.inc | 1 +
...er-Fix-not-properly-checking-for-sec.patch | 113 ++++
meta/recipes-devtools/flex/flex_2.6.4.bb | 5 +
meta/recipes-devtools/go/go-1.16.7.inc | 5 +
.../ruby/ruby/CVE-2021-31799.patch | 57 ++
.../ruby/ruby/CVE-2021-31810.patch | 258 ++++++++
.../ruby/ruby/CVE-2021-32066.patch | 102 +++
meta/recipes-devtools/ruby/ruby_3.0.1.bb | 3 +
.../squashfs-tools/files/CVE-2021-40153.patch | 253 ++++++++
.../squashfs-tools/squashfs-tools_git.bb | 1 +
meta/recipes-devtools/tcltk/tcl_8.6.11.bb | 3 +
.../mc/files/CVE-2021-36370.patch | 609 ++++++++++++++++++
meta/recipes-extended/mc/mc_4.8.26.bb | 1 +
.../linux/linux-yocto-rt_5.10.bb | 4 +-
.../linux/linux-yocto-rt_5.4.bb | 6 +-
.../linux/linux-yocto-tiny_5.10.bb | 6 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 22 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +-
...8b9eda402e4e96c4e3ce01e7ff95d3e10470.patch | 26 +
.../systemtap/systemtap_git.inc | 1 +
.../ffmpeg/ffmpeg/fix-CVE-2021-38171.patch | 40 ++
.../ffmpeg/ffmpeg/fix-CVE-2021-38291.patch | 54 ++
.../recipes-multimedia/ffmpeg/ffmpeg_4.3.2.bb | 2 +
.../apr/apr/CVE-2021-35940.patch | 58 ++
meta/recipes-support/apr/apr_1.7.0.bb | 1 +
.../sqlite/sqlite3/CVE-2021-36690.patch | 62 ++
meta/recipes-support/sqlite/sqlite3_3.35.0.bb | 4 +-
28 files changed, 1692 insertions(+), 35 deletions(-)
create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-shared-gatt-server-Fix-not-properly-checking-for-sec.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2021-31799.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2021-31810.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2021-32066.patch
create mode 100644 meta/recipes-devtools/squashfs-tools/files/CVE-2021-40153.patch
create mode 100644 meta/recipes-extended/mc/files/CVE-2021-36370.patch
create mode 100644 meta/recipes-kernel/systemtap/systemtap/ef5a8b9eda402e4e96c4e3ce01e7ff95d3e10470.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/fix-CVE-2021-38171.patch
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/fix-CVE-2021-38291.patch
create mode 100644 meta/recipes-support/apr/apr/CVE-2021-35940.patch
create mode 100644 meta/recipes-support/sqlite/sqlite3/CVE-2021-36690.patch
--
2.31.1
next reply other threads:[~2021-09-17 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 15:46 Anuj Mittal [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-29 14:40 [hardknott][PATCH 00/17] Pull request (cover letter only) Anuj Mittal
2021-06-15 7:17 [hardknott][PATCH 00/17] pull " Anuj Mittal
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.1631893475.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.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.