Patch review
cover Patch review
Please review this set of changes for kirkstone and have comments back by end of day Thursday, November 23
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6227
The following changes since commit 4bb6373e5f4a1330a063d1afe855d6c24d5461e7:
python3-jinja2: Fixed ptest result output as per the standard (2023-11-08 04:10:02 -1000)
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
Chaitanya Vadrevu (1):
go: Fix issue in DNS resolver
Deepthi Hemraj (2):
binutils: Fix CVE-2022-47007
binutils: Fix CVE-2022-48064
Lee Chee Yang (1):
ghostscript: ignore GhostPCL CVE-2023-38560
Meenali Gupta (5):
avahi: fix CVE-2023-38471
avahi: fix CVE-2023-38470
avahi: fix CVE-2023-38469
avahi: fix CVE-2023-38472
avahi: fix CVE-2023-38473
Niranjan Pradhan (1):
qemu 6.2.0: Fix CVE-2023-1544
Peter Marko (2):
go: ignore CVE-2023-45283 and CVE-2023-45284
goarch: Move Go architecture mapping to a library
Soumya Sambu (1):
sudo: upgrade 1.9.13p3 -> 1.9.15p2
Vijay Anusuri (1):
tiff: Backport fix for CVE-2023-41175
Wenlin Kang (1):
libxcrypt: fixed some build error for nativesdk with mingw
Yogita Urade (1):
grub: fix CVE-2023-4692
meta/classes/base.bbclass | 2 +-
meta/classes/goarch.bbclass | 27 +----
meta/lib/oe/go.py | 32 ++++++
.../grub/files/CVE-2023-4692.patch | 97 ++++++++++++++++
meta/recipes-bsp/grub/grub2.inc | 1 +
meta/recipes-connectivity/avahi/avahi_0.8.bb | 5 +
.../avahi/files/CVE-2023-38469.patch | 47 ++++++++
.../avahi/files/CVE-2023-38470.patch | 59 ++++++++++
.../avahi/files/CVE-2023-38471.patch | 73 ++++++++++++
.../avahi/files/CVE-2023-38472.patch | 46 ++++++++
.../avahi/files/CVE-2023-38473.patch | 108 ++++++++++++++++++
.../0001-Fix-for-compilation-on-Windows.patch | 37 ++++++
...dom-bytes.c-fixed-conversion-error-w.patch | 47 ++++++++
meta/recipes-core/libxcrypt/libxcrypt.inc | 4 +
.../binutils/binutils-2.38.inc | 2 +
.../binutils/0033-CVE-2022-47007.patch | 34 ++++++
.../binutils/0034-CVE-2022-48064.patch | 57 +++++++++
meta/recipes-devtools/go/go-1.17.13.inc | 5 +-
...Fix-issue-with-DNS-not-being-updated.patch | 51 +++++++++
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2023-1544.patch | 70 ++++++++++++
.../ghostscript/ghostscript_9.55.0.bb | 3 +
...me.c-correctly-include-header-for-ou.patch | 25 ----
meta/recipes-extended/sudo/sudo.inc | 5 +-
.../{sudo_1.9.13p3.bb => sudo_1.9.15p2.bb} | 3 +-
.../libtiff/tiff/CVE-2023-41175.patch | 69 +++++++++++
meta/recipes-multimedia/libtiff/tiff_4.3.0.bb | 1 +
27 files changed, 854 insertions(+), 57 deletions(-)
create mode 100644 meta/lib/oe/go.py
create mode 100644 meta/recipes-bsp/grub/files/CVE-2023-4692.patch
create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38469.patch
create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38470.patch
create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38471.patch
create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38472.patch
create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38473.patch
create mode 100644 meta/recipes-core/libxcrypt/files/0001-Fix-for-compilation-on-Windows.patch
create mode 100644 meta/recipes-core/libxcrypt/files/0001-lib-util-get-random-bytes.c-fixed-conversion-error-w.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/0034-CVE-2022-48064.patch
create mode 100644 meta/recipes-devtools/go/go-1.20/0010-net-Fix-issue-with-DNS-not-being-updated.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-1544.patch
delete mode 100644 meta/recipes-extended/sudo/files/0001-lib-util-mksigname.c-correctly-include-header-for-ou.patch
rename meta/recipes-extended/sudo/{sudo_1.9.13p3.bb => sudo_1.9.15p2.bb} (92%)
create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2023-41175.patchSignature · 1 line
2.34.1
PATCH 1/16 tiff: Backport fix for CVE-2023-41175
From: Vijay Anusuri <[email protected]>
Upstream-Status: Backport [https://gitlab.com/libtiff/libtiff/-/commit/6e2dac5f904496d127c92ddc4e56eccfca25c2ee]
Reference: https://security-tracker.debian.org/tracker/CVE-2023-41175
--- .../libtiff/tiff/CVE-2023-41175.patch | 69 +++++++++++++++++++ meta/recipes-multimedia/libtiff/tiff_4.3.0.bb | 1 + 2 files changed, 70 insertions(+) create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2023-41175.patch
meta/recipes-multimedia/libtiff/tiff/CVE-2023-41175.patch new file +69 -0
@@ -0,0 +1,69 @@ +From 6e2dac5f904496d127c92ddc4e56eccfca25c2ee Mon Sep 17 00:00:00 2001 +From: Arie Haenel <[email protected]> +Date: Wed, 19 Jul 2023 19:40:01 +0000 +Subject: [PATCH] raw2tiff: fix integer overflow and bypass of the check (fixes #592) + +Upstream-Status: Backport [https://gitlab.com/libtiff/libtiff/-/commit/6e2dac5f904496d127c92ddc4e56eccfca25c2ee] +CVE: CVE-2023-41175 +Signed-off-by: Vijay Anusuri <[email protected]> +--- + tools/raw2tiff.c | 29 +++++++++++++++++++++++++++++ + 1 file changed, 29 insertions(+) + +diff --git a/tools/raw2tiff.c b/tools/raw2tiff.c +index dfee715..253c023 100644 +--- a/tools/raw2tiff.c ++++ b/tools/raw2tiff.c +@@ -36,6 +36,7 @@ + #include <sys/types.h> + #include <math.h> + #include <ctype.h> ++#include <limits.h> + + #ifdef HAVE_UNISTD_H + # include <unistd.h> +@@ -101,6 +102,7 @@ main(int argc, char* argv[]) + int fd; + char *outfilename = NULL; + TIFF *out; ++ uint32_t temp_limit_check = 0; /* temp for integer overflow checking*/ + + uint32_t row, col, band; + int c; +@@ -212,6 +214,33 @@ main(int argc, char* argv[]) + if (guessSize(fd, dtype, hdr_size, nbands, swab, &width, &length) < 0) + return EXIT_FAILURE; + ++ /* check for integer overflow in */ ++ /* hdr_size + (*width) * (*length) * nbands * depth */ ++ ++ if ((width == 0) || (length == 0) ){ ++ fprintf(stderr, "Too large nbands value specified.\n"); ++ return (EXIT_FAILURE); ++ } ++ ++ temp_limit_check = nbands * depth; ++ ++ if ( !temp_limit_check || length > ( UINT_MAX / temp_limit_check ) ) { ++ fprintf(stderr, "Too large length size specified.\n"); ++ return (EXIT_FAILURE); ++ } ++ temp_limit_check = temp_limit_check * length; ++ ++ if ( !temp_limit_check || width > ( UINT_MAX / temp_limit_check ) ) { ++ fprintf(stderr, "Too large width size specified.\n"); ++ return (EXIT_FAILURE); ++ } ++ temp_limit_check = temp_limit_check * width; ++ ++ if ( !temp_limit_check || hdr_size > ( UINT_MAX - temp_limit_check ) ) { ++ fprintf(stderr, "Too large header size specified.\n"); ++ return (EXIT_FAILURE); ++ } ++ + if (outfilename == NULL) + outfilename = argv[optind+1]; + out = TIFFOpen(outfilename, "w"); +-- +2.25.1 +
meta/recipes-multimedia/libtiff/tiff_4.3.0.bb +1 -0
@@ -46,6 +46,7 @@ SRC_URI = "http://download.osgeo.org/libtiff/tiff-${PV}.tar.gz \ file://CVE-2022-40090.patch \ file://CVE-2023-1916.patch \ file://CVE-2023-40745.patch \ + file://CVE-2023-41175.patch \ " SRC_URI[sha256sum] = "0e46e5acb087ce7d1ac53cf4f56a09b221537fc86dfc5daaad1c2e89e1b37ac8"
Signature · 1 line
2.34.1
PATCH 2/16 grub: fix CVE-2023-4692
In reply to Steve SakomanFrom: Yogita Urade <[email protected]>
An out-of-bounds write flaw was found in grub2's NTFS filesystem driver. This issue may allow an attacker to present a specially crafted NTFS filesystem image, leading to grub's heap metadata corruption. In some circumstances, the attack may also corrupt the UEFI firmware heap metadata. As a result, arbitrary code execution and secure boot protection bypass may be achieved.
References:
https://nvd.nist.gov/vuln/detail/CVE-2023-4692
https://bugzilla.redhat.com/show_bug.cgi?id=2236613
--- .../grub/files/CVE-2023-4692.patch | 97 +++++++++++++++++++ meta/recipes-bsp/grub/grub2.inc | 1 + 2 files changed, 98 insertions(+) create mode 100644 meta/recipes-bsp/grub/files/CVE-2023-4692.patch
meta/recipes-bsp/grub/files/CVE-2023-4692.patch new file +97 -0
@@ -0,0 +1,97 @@ +From 43651027d24e62a7a463254165e1e46e42aecdea Mon Sep 17 00:00:00 2001 +From: Maxim Suhanov <[email protected]> +Date: Thu, 16 Nov 2023 07:21:50 +0000 +Subject: [PATCH] fs/ntfs: Fix an OOB write when parsing the $ATTRIBUTE_LIST + attribute for the $MFT file + +When parsing an extremely fragmented $MFT file, i.e., the file described +using the $ATTRIBUTE_LIST attribute, current NTFS code will reuse a buffer +containing bytes read from the underlying drive to store sector numbers, +which are consumed later to read data from these sectors into another buffer. + +These sectors numbers, two 32-bit integers, are always stored at predefined +offsets, 0x10 and 0x14, relative to first byte of the selected entry within +the $ATTRIBUTE_LIST attribute. Usually, this won't cause any problem. + +However, when parsing a specially-crafted file system image, this may cause +the NTFS code to write these integers beyond the buffer boundary, likely +causing the GRUB memory allocator to misbehave or fail. These integers contain +values which are controlled by on-disk structures of the NTFS file system. + +Such modification and resulting misbehavior may touch a memory range not +assigned to the GRUB and owned by firmware or another EFI application/driver. + +This fix introduces checks to ensure that these sector numbers are never +written beyond the boundary. + +Fixes: CVE-2023-4692 + +Reported-by: Maxim Suhanov <[email protected]> +Signed-off-by: Maxim Suhanov <[email protected]> +Reviewed-by: Daniel Kiper <[email protected]> + +CVE: CVE-2023-4692 +Upstream-Status: Backport [https://git.savannah.gnu.org/cgit/grub.git/commit/?id=43651027d24e62a7a463254165e1e46e42aecdea] + +Signed-off-by: Yogita Urade <[email protected]> +--- + grub-core/fs/ntfs.c | 18 +++++++++++++++++- + 1 file changed, 17 insertions(+), 1 deletion(-) + +diff --git a/grub-core/fs/ntfs.c b/grub-core/fs/ntfs.c +index 2f34f76..6009e49 100644 +--- a/grub-core/fs/ntfs.c ++++ b/grub-core/fs/ntfs.c +@@ -184,7 +184,7 @@ find_attr (struct grub_ntfs_attr *at, grub_uint8_t attr) + } + if (at->attr_end) + { +- grub_uint8_t *pa; ++ grub_uint8_t *pa, *pa_end; + + at->emft_buf = grub_malloc (at->mft->data->mft_size << GRUB_NTFS_BLK_SHR); + if (at->emft_buf == NULL) +@@ -209,11 +209,13 @@ find_attr (struct grub_ntfs_attr *at, grub_uint8_t attr) + } + at->attr_nxt = at->edat_buf; + at->attr_end = at->edat_buf + u32at (pa, 0x30); ++ pa_end = at->edat_buf + n; + } + else + { + at->attr_nxt = at->attr_end + u16at (pa, 0x14); + at->attr_end = at->attr_end + u32at (pa, 4); ++ pa_end = at->mft->buf + (at->mft->data->mft_size << GRUB_NTFS_BLK_SHR); + } + at->flags |= GRUB_NTFS_AF_ALST; + while (at->attr_nxt < at->attr_end) +@@ -230,6 +232,13 @@ find_attr (struct grub_ntfs_attr *at, grub_uint8_t attr) + at->flags |= GRUB_NTFS_AF_GPOS; + at->attr_cur = at->attr_nxt; + pa = at->attr_cur; ++ ++ if ((pa >= pa_end) || (pa_end - pa < 0x18)) ++ { ++ grub_error (GRUB_ERR_BAD_FS, "can\'t parse attribute list"); ++ return NULL; ++ } ++ + grub_set_unaligned32 ((char *) pa + 0x10, + grub_cpu_to_le32 (at->mft->data->mft_start)); + grub_set_unaligned32 ((char *) pa + 0x14, +@@ -240,6 +249,13 @@ find_attr (struct grub_ntfs_attr *at, grub_uint8_t attr) + { + if (*pa != attr) + break; ++ ++ if ((pa >= pa_end) || (pa_end - pa < 0x18)) ++ { ++ grub_error (GRUB_ERR_BAD_FS, "can\'t parse attribute list"); ++ return NULL; ++ } ++ + if (read_attr + (at, pa + 0x10, + u32at (pa, 0x10) * (at->mft->data->mft_size << GRUB_NTFS_BLK_SHR), +-- +2.40.0
meta/recipes-bsp/grub/grub2.inc +1 -0
@@ -38,6 +38,7 @@ SRC_URI = "${GNU_MIRROR}/grub/grub-${PV}.tar.gz \ file://loader-efi-chainloader-Simplify-the-loader-state.patch \ file://commands-boot-Add-API-to-pass-context-to-loader.patch \ file://CVE-2022-28736-loader-efi-chainloader-Use-grub_loader_set_ex.patch \ + file://CVE-2023-4692.patch \ " SRC_URI[sha256sum] = "23b64b4c741569f9426ed2e3d0e6780796fca081bee4c99f62aa3f53ae803f5f"
Signature · 1 line
2.34.1
PATCH 3/16 qemu 6.2.0: Fix CVE-2023-1544
In reply to Steve SakomanFrom: Niranjan Pradhan <[email protected]>
Upstream Repository: https://gitlab.com/qemu-project/qemu.git
Bug Details: https://nvd.nist.gov/vuln/detail/CVE-2023-1544
Type: Security Fix
CVE: CVE-2023-1544
Score: 6.3
Patch: https://gitlab.com/qemu-project/qemu/-/commit/85fc35afa93c
--- meta/recipes-devtools/qemu/qemu.inc | 1 + .../qemu/qemu/CVE-2023-1544.patch | 70 +++++++++++++++++++ 2 files changed, 71 insertions(+) create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-1544.patch
meta/recipes-devtools/qemu/qemu.inc +1 -0
@@ -101,6 +101,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \ file://CVE-2023-3354.patch \ file://CVE-2023-3180.patch \ file://CVE-2021-3638.patch \ + file://CVE-2023-1544.patch \ " UPSTREAM_CHECK_REGEX = "qemu-(?P<pver>\d+(\.\d+)+)\.tar"
meta/recipes-devtools/qemu/qemu/CVE-2023-1544.patch new file +70 -0
70 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 4/16 avahi: fix CVE-2023-38471
In reply to Steve SakomanFrom: Meenali Gupta <[email protected]>
A vulnerability was found in Avahi. A reachable assertion exists in the dbus_set_host_name function.
--- meta/recipes-connectivity/avahi/avahi_0.8.bb | 1 + .../avahi/files/CVE-2023-38471.patch | 73 +++++++++++++++++++ 2 files changed, 74 insertions(+) create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38471.patch
meta/recipes-connectivity/avahi/avahi_0.8.bb +1 -0
@@ -26,6 +26,7 @@ SRC_URI = "https://github.com/lathiat/avahi/releases/download/v${PV}/avahi-${PV} file://0001-Fix-opening-etc-resolv.conf-error.patch \ file://handle-hup.patch \ file://local-ping.patch \ + file://CVE-2023-38471.patch \ " UPSTREAM_CHECK_URI = "https://github.com/lathiat/avahi/releases/"
meta/recipes-connectivity/avahi/files/CVE-2023-38471.patch new file +73 -0
73 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 5/16 avahi: fix CVE-2023-38470
In reply to Steve SakomanFrom: Meenali Gupta <[email protected]>
A vulnerability was found in Avahi. A reachable assertion exists in the avahi_escape_label() function.
--- meta/recipes-connectivity/avahi/avahi_0.8.bb | 1 + .../avahi/files/CVE-2023-38470.patch | 59 +++++++++++++++++++ 2 files changed, 60 insertions(+) create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38470.patch
meta/recipes-connectivity/avahi/avahi_0.8.bb +1 -0
@@ -27,6 +27,7 @@ SRC_URI = "https://github.com/lathiat/avahi/releases/download/v${PV}/avahi-${PV} file://handle-hup.patch \ file://local-ping.patch \ file://CVE-2023-38471.patch \ + file://CVE-2023-38470.patch \ " UPSTREAM_CHECK_URI = "https://github.com/lathiat/avahi/releases/"
meta/recipes-connectivity/avahi/files/CVE-2023-38470.patch new file +59 -0
59 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 6/16 avahi: fix CVE-2023-38469
In reply to Steve SakomanFrom: Meenali Gupta <[email protected]>
A vulnerability was found in Avahi, where a reachable assertion exists in avahi_dns_packet_append_record.
--- meta/recipes-connectivity/avahi/avahi_0.8.bb | 1 + .../avahi/files/CVE-2023-38469.patch | 47 +++++++++++++++++++ 2 files changed, 48 insertions(+) create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38469.patch
meta/recipes-connectivity/avahi/avahi_0.8.bb +1 -0
@@ -28,6 +28,7 @@ SRC_URI = "https://github.com/lathiat/avahi/releases/download/v${PV}/avahi-${PV} file://local-ping.patch \ file://CVE-2023-38471.patch \ file://CVE-2023-38470.patch \ + file://CVE-2023-38469.patch \ " UPSTREAM_CHECK_URI = "https://github.com/lathiat/avahi/releases/"
meta/recipes-connectivity/avahi/files/CVE-2023-38469.patch new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 7/16 avahi: fix CVE-2023-38472
In reply to Steve SakomanFrom: Meenali Gupta <[email protected]>
A vulnerability was found in Avahi. A reachable assertion exists in the avahi_rdata_parse() function.
--- meta/recipes-connectivity/avahi/avahi_0.8.bb | 1 + .../avahi/files/CVE-2023-38472.patch | 46 +++++++++++++++++++ 2 files changed, 47 insertions(+) create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38472.patch
meta/recipes-connectivity/avahi/avahi_0.8.bb +1 -0
@@ -29,6 +29,7 @@ SRC_URI = "https://github.com/lathiat/avahi/releases/download/v${PV}/avahi-${PV} file://CVE-2023-38471.patch \ file://CVE-2023-38470.patch \ file://CVE-2023-38469.patch \ + file://CVE-2023-38472.patch \ " UPSTREAM_CHECK_URI = "https://github.com/lathiat/avahi/releases/"
meta/recipes-connectivity/avahi/files/CVE-2023-38472.patch new file +46 -0
46 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 8/16 avahi: fix CVE-2023-38473
In reply to Steve SakomanFrom: Meenali Gupta <[email protected]>
A vulnerability was found in Avahi. A reachable assertion exists in the avahi_alternative_host_name() function.
--- meta/recipes-connectivity/avahi/avahi_0.8.bb | 1 + .../avahi/files/CVE-2023-38473.patch | 108 ++++++++++++++++++ 2 files changed, 109 insertions(+) create mode 100644 meta/recipes-connectivity/avahi/files/CVE-2023-38473.patch
meta/recipes-connectivity/avahi/avahi_0.8.bb +1 -0
@@ -30,6 +30,7 @@ SRC_URI = "https://github.com/lathiat/avahi/releases/download/v${PV}/avahi-${PV} file://CVE-2023-38470.patch \ file://CVE-2023-38469.patch \ file://CVE-2023-38472.patch \ + file://CVE-2023-38473.patch \ " UPSTREAM_CHECK_URI = "https://github.com/lathiat/avahi/releases/"
meta/recipes-connectivity/avahi/files/CVE-2023-38473.patch new file +108 -0
108 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 9/16 binutils: Fix CVE-2022-47007
In reply to Steve SakomanFrom: Deepthi Hemraj <[email protected]>
--- .../binutils/binutils-2.38.inc | 1 + .../binutils/0033-CVE-2022-47007.patch | 34 +++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch
meta/recipes-devtools/binutils/binutils-2.38.inc +1 -0
@@ -67,5 +67,6 @@ SRC_URI = "\ file://0031-CVE-2022-47695.patch \ file://CVE-2022-48063.patch \ file://0032-CVE-2022-47010.patch \ + file://0033-CVE-2022-47007.patch \ " S = "${WORKDIR}/git"
meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch new file +34 -0
@@ -0,0 +1,34 @@ +From: Alan Modra <[email protected]> +Date: Thu, 16 Jun 2022 23:30:41 +0000 (+0930) +Subject: PR29254, memory leak in stab_demangle_v3_arg +X-Git-Tag: binutils-2_39~237 +X-Git-Url: https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=0ebc886149c22aceaf8ed74267821a59ca9d03eb + +PR29254, memory leak in stab_demangle_v3_arg + + PR 29254 + * stabs.c (stab_demangle_v3_arg): Free dt on failure path. + +Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=0ebc886149c22aceaf8ed74267821a59ca9d03eb] + +CVE: CVE-2022-47007 + +Signed-off-by: Deepthi Hemraj <[email protected]> +--- + +diff --git a/binutils/stabs.c b/binutils/stabs.c +index 2b5241637c1..796ff85b86a 100644 +--- a/binutils/stabs.c ++++ b/binutils/stabs.c +@@ -5467,7 +5467,10 @@ stab_demangle_v3_arg (void *dhandle, struct stab_handle *info, + dc->u.s_binary.right, + &varargs); + if (pargs == NULL) +- return NULL; ++ { ++ free (dt); ++ return NULL; ++ } + + return debug_make_function_type (dhandle, dt, pargs, varargs); + }
Signature · 1 line
2.34.1
PATCH 10/16 binutils: Fix CVE-2022-48064
In reply to Steve SakomanFrom: Deepthi Hemraj <[email protected]>
--- .../binutils/binutils-2.38.inc | 1 + .../binutils/0034-CVE-2022-48064.patch | 57 +++++++++++++++++++ 2 files changed, 58 insertions(+) create mode 100644 meta/recipes-devtools/binutils/binutils/0034-CVE-2022-48064.patch
meta/recipes-devtools/binutils/binutils-2.38.inc +1 -0
@@ -68,5 +68,6 @@ SRC_URI = "\ file://CVE-2022-48063.patch \ file://0032-CVE-2022-47010.patch \ file://0033-CVE-2022-47007.patch \ + file://0034-CVE-2022-48064.patch \ " S = "${WORKDIR}/git"
meta/recipes-devtools/binutils/binutils/0034-CVE-2022-48064.patch new file +57 -0
57 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 11/16 ghostscript: ignore GhostPCL CVE-2023-38560
In reply to Steve SakomanFrom: Lee Chee Yang <[email protected]>
issue in GhostPCL.
GhostPCL not part of this GhostScript recipe.
--- meta/recipes-extended/ghostscript/ghostscript_9.55.0.bb | 3 +++ 1 file changed, 3 insertions(+)
meta/recipes-extended/ghostscript/ghostscript_9.55.0.bb +3 -0
@@ -23,6 +23,9 @@ UPSTREAM_CHECK_REGEX = "(?P<pver>\d+(\.\d+)+)\.tar" # however we use an external jpeg which doesn't have the issue. CVE_CHECK_IGNORE += "CVE-2013-6629" +# Issue in the GhostPCL. GhostPCL not part of this GhostScript recipe. +CVE_CHECK_IGNORE += "CVE-2023-38560" + def gs_verdir(v): return "".join(v.split("."))
Signature · 1 line
2.34.1
PATCH 12/16 go: ignore CVE-2023-45283 and CVE-2023-45284
In reply to Steve SakomanFrom: Peter Marko <[email protected]>
These CVEs affect path handling on Windows.
--- meta/recipes-devtools/go/go-1.17.13.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
meta/recipes-devtools/go/go-1.17.13.inc +2 -2
@@ -54,5 +54,5 @@ SRC_URI[main.sha256sum] = "a1a48b23afb206f95e7bbaa9b898d965f90826f6f1d1fc0c1d784 # https://github.com/golang/go/issues/30999#issuecomment-910470358 CVE_CHECK_IGNORE += "CVE-2021-29923" -# This is specific to Microsoft Windows -CVE_CHECK_IGNORE += "CVE-2022-41716" +# This are specific to Microsoft Windows +CVE_CHECK_IGNORE += "CVE-2022-41716 CVE-2023-45283 CVE-2023-45284"
Signature · 1 line
2.34.1
PATCH 13/16 sudo: upgrade 1.9.13p3 -> 1.9.15p2
In reply to Steve SakomanFrom: Soumya Sambu <[email protected]>
License-update: file removed upstream
Drop patch as issue fixed upstream.
Changelog:
===========
1.9.15p2
* Fixed a bug on BSD systems where sudo would not restore the terminal settings on exit if the terminal had parity enabled. GitHub issue #326.
1.9.15p1
* Fixed a bug introduced in sudo 1.9.15 that prevented LDAP-based sudoers from being able to read the ldap.conf file. GitHub issue #325.
1.9.15
* Fixed an undefined symbol problem on older versions of macOS when "intercept" or "log_subcmds" are enabled in sudoers. GitHub issue #276.
* Fixed "make check" failure related to getpwent(3) wrapping on NetBSD.
* Fixed the warning message for "sudo -l command" when the command is not permitted. There was a missing space between "list" and the actual command due to changes in sudo 1.9.14.
* Fixed a bug where output could go to the wrong terminal if "use_pty" is enabled (the default) and the standard input, output or error is redirected to a different terminal. Bug #1056.
* The visudo utility will no longer create an empty file when the specified sudoers file does not exist and the user exits the editor without making any changes. GitHub issue #294.
* The AIX and Solaris sudo packages on www.sudo.ws now support "log_subcmds" and "intercept" with both 32-bit and 64-bit binaries. Previously, they only worked when running binaries with the same word size as the sudo binary. GitHub issue #289.
* The sudoers source is now logged in the JSON event log. This makes it possible to tell which rule resulted in a match.
* Running "sudo -ll command" now produces verbose output that includes matching rule as well as the path to the sudoers file the matching rule came from. For LDAP sudoers, the name of the matching sudoRole is printed instead.
* The embedded copy of zlib has been updated to version 1.3.
* The sudoers plugin has been modified to make it more resilient to ROWHAMMER attacks on authentication and policy matching. This addresses CVE-2023-42465.
* The sudoers plugin now constructs the user time stamp file path name using the user-ID instead of the user name. This avoids a potential problem with user names that contain a path separator ('/') being interpreted as part of the path name. A similar issue in sudo-rs has been assigned CVE-2023-42456.
* A path separator ('/') in a user, group or host name is now replaced with an underbar character ('_') when expanding escapes in @include and @includedir directives as well as the "iolog_file" and "iolog_dir" sudoers Default settings.
* The "intercept_verify" sudoers option is now only applied when the "intercept" option is set in sudoers. Previously, it was also applied when "log_subcmds" was enabled. Sudo 1.9.14 contained an incorrect fix for this. Bug #1058.
* Changes to terminal settings are now performed atomically, where possible. If the command is being run in a pseudo-terminal and the user's terminal is already in raw mode, sudo will not change the user's terminal settings. This prevents concurrent sudo processes from restoring the terminal settings to the wrong values. GitHub issue #312.
* Reverted a change from sudo 1.9.4 that resulted in PAM session modules being called with the environment of the command to be run instead of the environment of the invoking user. GitHub issue #318.
* New Indonesian translation from translationproject.org.
* The sudo_logsrvd server will now raise its open file descriptor limit to the maximum allowed value when it starts up. Each connection can require up to nine open file descriptors so the default soft limit may be too low.
* Better log message when rejecting a command if the "intercept" option is enabled and the "intercept_allow_setid" option is disabled. Previously, "command not allowed" would be logged and the user had no way of knowing what the actual problem was.
* Sudo will now log the invoking user's environment as "submitenv" in the JSON logs. The command's environment ("runenv") is no longer logged for commands rejected by the sudoers file or an approval plugin.
1.9.14p3
* Fixed a crash with Python 3.12 when the sudo Python plugin is unloaded. This only affects "make check" for the Python plugin.
* Adapted the sudo Python plugin test output to match Python 3.12.
1.9.14p2
* Fixed a crash on Linux systems introduced in version 1.9.14 when running a command with a NULL argv[0] if "log_subcmds" or "intercept" is enabled in sudoers.
* Fixed a problem with "stair-stepped" output when piping or redirecting the output of a sudo command that takes user input.
* Fixed a bug introduced in sudo 1.9.14 that affects matching sudoers rules containing a Runas_Spec with an empty Runas user. These rules should only match when sudo's -g option is used but were matching even without the -g option. GitHub issue #290.
1.9.14p1
* Fixed an invalid free bug in sudo_logsrvd that was introduced in version 1.9.14 which could cause sudo_logsrvd to crash.
* The sudoers plugin no longer tries to send the terminal name to the log server when no terminal is present. This bug was introduced in version 1.9.14.
1.9.14
* Fixed a bug where if the "intercept" or "log_subcmds" sudoers option was enabled and a sub-command was run where the first entry of the argument vector didn't match the command being run. This resulted in commands like "sudo su -" being killed due to the mismatch. Bug #1050.
* The sudoers plugin now canonicalizes command path names before matching (where possible). This fixes a bug where sudo could execute the wrong path if there are multiple symbolic links with the same target and the same base name in sudoers that a user is allowed to run. GitHub issue #228.
* Improved command matching when a chroot is specified in sudoers. The sudoers plugin will now change the root directory id needed before performing command matching. Previously, the root directory was simply prepended to the path that was being processed.
* When NETGROUP_BASE is set in the ldap.conf file, sudo will now perform its own netgroup lookups of the host name instead of using the system innetgr(3) function. This guarantees that user and host netgroup lookups are performed using the same LDAP server (or servers).
* Fixed a bug introduced in sudo 1.9.13 that resulted in a missing " ; " separator between environment variables and the command in log entries.
* The visudo utility now displays a warning when it ignores a file in an include dir such as /etc/sudoers.d.
* When running a command in a pseudo-terminal, sudo will initialize the terminal settings even if it is the background process. Previously, sudo only initialized the pseudo-terminal when running in the foreground. This fixes an issue where a program that checks the window size would read the wrong value when sudo was running in the background.
* Fixed a bug where only the first two digits of the TSID field being was logged. Bug #1046.
* The "use_pty" sudoers option is now enabled by default. To restore the historic behavior where a command is run in the user's terminal, add "Defaults !use_pty" to the sudoers file. GitHub issue #258.
* Sudo's "-b" option now works when the command is run in a pseudo-terminal.
* When disabling core dumps, sudo now only modifies the soft limit and leaves the hard limit as-is. This avoids problems on Linux when sudo does not have CAP_SYS_RESOURCE, which may be the case when run inside a container. GitHub issue #42.
* Sudo configuration file paths have been converted to colon-separated lists of paths. This makes it possible to have configuration files on a read-only file system while still allowing for local modifications in a different (writable) directory. The new --enable-adminconf configure option can be used to specify a directory that is searched for configuration files in preference to the sysconfdir (which is usually /etc).
* The NETGROUP_QUERY ldap.conf parameter can now be disabled for LDAP servers that do not support querying the nisNetgroup object by its nisNetgroupTriple attribute, while still allowing sudo to query the LDAP server directly to determine netgroup membership.
* Fixed a long-standing bug where a sudoers rule without an explicit runas list allowed the user to run a command as root and any group instead of just one of the groups that root is a member of. For example, a rule such as "myuser ALL = ALL" would permit "sudo -u root -g othergroup" even if root did not belong to "othergroup".
* Fixed a bug where a sudoers rule with an explicit runas list allowed a user to run sudo commands as themselves. For example, a rule such as "myuser ALL = (root) ALL", "myuser" should only allow commands to be run as root (optionally using one of root's groups). However, the rule also allowed the user to run "sudo -u myuser -g myuser command".
* Fixed a bug that prevented the user from specifying a group on the command line via "sudo -g" if the rule's Runas_Spec contained a Runas_Alias.
* Sudo now requires a C compiler that conforms to ISO C99 or higher to build.
---
...me.c-correctly-include-header-for-ou.patch | 25 -------------------
meta/recipes-extended/sudo/sudo.inc | 5 ++--
.../{sudo_1.9.13p3.bb => sudo_1.9.15p2.bb} | 3 +--
3 files changed, 3 insertions(+), 30 deletions(-)
delete mode 100644 meta/recipes-extended/sudo/files/0001-lib-util-mksigname.c-correctly-include-header-for-ou.patch
rename meta/recipes-extended/sudo/{sudo_1.9.13p3.bb => sudo_1.9.15p2.bb} (92%)meta/recipes-extended/sudo/files/0001-lib-util-mksigname.c-correctly-include-header-for-ou.patch deleted +0 -25
@@ -1,25 +0,0 @@ -From f993c5c88faacc43971899aae2168ffb3e34dc80 Mon Sep 17 00:00:00 2001 -From: Alexander Kanavin <[email protected]> -Date: Fri, 24 Sep 2021 13:36:24 +0200 -Subject: [PATCH] lib/util/mksigname.c: correctly include header for out of - tree builds - -Upstream-Status: Submitted [https://github.com/sudo-project/sudo/pull/123] -Signed-off-by: Alexander Kanavin <[email protected]> ---- - lib/util/mksigname.c | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/lib/util/mksigname.c b/lib/util/mksigname.c -index de8b1ad..0a69e7e 100644 ---- a/lib/util/mksigname.c -+++ b/lib/util/mksigname.c -@@ -36,7 +36,7 @@ main(int argc, char *argv[]) - { - unsigned int i; - --#include "mksigname.h" -+#include "lib/util/mksigname.h" - - printf("const char *const sudo_sys_signame[] = {\n"); - for (i = 0; i < nitems(sudo_sys_signame); i++) {
meta/recipes-extended/sudo/sudo.inc +2 -3
@@ -8,7 +8,6 @@ LIC_FILES_CHKSUM = "file://LICENSE.md;md5=5100e20d35f9015f9eef6bdb27ba194f \ file://plugins/sudoers/redblack.c;beginline=1;endline=46;md5=03e35317699ba00b496251e0dfe9f109 \ file://lib/util/reallocarray.c;beginline=3;endline=15;md5=397dd45c7683e90b9f8bf24638cf03bf \ file://lib/util/fnmatch.c;beginline=3;endline=27;md5=004d7d2866ba1f5b41174906849d2e0f \ - file://lib/util/getcwd.c;beginline=2;endline=27;md5=50f8d9667750e18dea4e84a935c12009 \ file://lib/util/glob.c;beginline=2;endline=31;md5=2852f68687544e3eb8a0a61665506f0e \ file://lib/util/snprintf.c;beginline=3;endline=33;md5=b70df6179969e38fcf68da91b53b8029 \ file://include/sudo_queue.h;beginline=2;endline=27;md5=ad578e9664d17a010b63e4bc0576ee8d \
@@ -29,12 +28,12 @@ EXTRA_OECONF = "--with-editor=${base_bindir}/vi --with-env-editor" EXTRA_OECONF:append:libc-musl = " --disable-hardening " do_compile:prepend () { - # Remove build host references from sudo_usage.h + # Remove build host references from config.h sed -i \ -e 's,--with-libtool-sysroot=${STAGING_DIR_TARGET},,g' \ -e 's,--build=${BUILD_SYS},,g' \ -e 's,--host=${HOST_SYS},,g' \ - ${B}/src/sudo_usage.h + ${B}/config.h } # Explicitly create ${localstatedir}/lib before do_install to ensure
meta/recipes-extended/sudo/sudo_1.9.15p2.bb renamed from meta/recipes-extended/sudo/sudo_1.9.13p3.bb +1 -2
@@ -3,12 +3,11 @@ require sudo.inc SRC_URI = "https://www.sudo.ws/dist/sudo-${PV}.tar.gz \ ${@bb.utils.contains('DISTRO_FEATURES', 'pam', '${PAM_SRC_URI}', '', d)} \ file://0001-sudo.conf.in-fix-conflict-with-multilib.patch \ - file://0001-lib-util-mksigname.c-correctly-include-header-for-ou.patch \ " PAM_SRC_URI = "file://sudo.pam" -SRC_URI[sha256sum] = "92334a12bb93e0c056b09f53e255ccb7d6f67c6350e2813cd9593ceeca78560b" +SRC_URI[sha256sum] = "199c0cdbfa7efcfffa9c88684a8e2fb206a62b70a316507e4a91c89c873bbcc8" DEPENDS += " virtual/crypt ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}" RDEPENDS:${PN} += " ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'pam-plugin-limits pam-plugin-keyinit', '', d)}"
Signature · 1 line
2.34.1
PATCH 14/16 go: Fix issue in DNS resolver
In reply to Steve SakomanFrom: Chaitanya Vadrevu <[email protected]>
This change adds a patch that is a partial backport of an upstream commit[1].
It fixes a bug in go's DNS resolver that was causing a docker issue where the first "docker pull" always fails after system boot if docker daemon is started before networking is completely up.
[1] https://github.com/golang/go/commit/d52883f443e1d564b0300acdd382af1769bf0477
--- meta/recipes-devtools/go/go-1.17.13.inc | 1 + ...Fix-issue-with-DNS-not-being-updated.patch | 51 +++++++++++++++++++ 2 files changed, 52 insertions(+) create mode 100644 meta/recipes-devtools/go/go-1.20/0010-net-Fix-issue-with-DNS-not-being-updated.patch
meta/recipes-devtools/go/go-1.17.13.inc +1 -0
@@ -16,6 +16,7 @@ SRC_URI += "\ file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \ file://0001-exec.go-do-not-write-linker-flags-into-buildids.patch \ file://0001-src-cmd-dist-buildgo.go-do-not-hardcode-host-compile.patch \ + file://0010-net-Fix-issue-with-DNS-not-being-updated.patch \ file://CVE-2022-27664.patch \ file://0001-net-http-httputil-avoid-query-parameter-smuggling.patch \ file://CVE-2022-41715.patch \
meta/recipes-devtools/go/go-1.20/0010-net-Fix-issue-with-DNS-not-being-updated.patch new file +51 -0
51 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH 15/16 goarch: Move Go architecture mapping to a library
In reply to Steve SakomanFrom: Peter Marko <[email protected]>
Other spaces uses the Go architecture definitions as their own (for example, container arches are defined to be Go arches). To make it easier for other places to use this mapping, move the code that does the translation of OpenEmbedded arches to Go arches to a library.
(From oe-core rev: 3e86f72fc2e1cc2e5ea4b4499722d736941167ce)
This commit together with meta-virtualization commit 115f6367f37095415f289fb6981cda9608ac72ff broke meta-virtualization master used with meta-lts-mixins kirkstone/go which is our primary usecase for having kirkstone/go mixin layer
Manually crafted since cherry-pick had too many conflicts:
* different path to classes
* additional architecture loongarch64
* different way how to import library
--- meta/classes/base.bbclass | 2 +- meta/classes/goarch.bbclass | 27 +++------------------------ meta/lib/oe/go.py | 32 ++++++++++++++++++++++++++++++++ 3 files changed, 36 insertions(+), 25 deletions(-) create mode 100644 meta/lib/oe/go.py
meta/classes/base.bbclass +1 -1
@@ -12,7 +12,7 @@ inherit logging OE_EXTRA_IMPORTS ?= "" -OE_IMPORTS += "os sys time oe.path oe.utils oe.types oe.package oe.packagegroup oe.sstatesig oe.lsb oe.cachedpath oe.license oe.qa oe.reproducible oe.rust ${OE_EXTRA_IMPORTS}" +OE_IMPORTS += "os sys time oe.path oe.utils oe.types oe.package oe.packagegroup oe.sstatesig oe.lsb oe.cachedpath oe.license oe.qa oe.reproducible oe.rust oe.go ${OE_EXTRA_IMPORTS}" OE_IMPORTS[type] = "list" PACKAGECONFIG_CONFARGS ??= ""
meta/classes/goarch.bbclass +3 -24
@@ -61,31 +61,10 @@ SECURITY_NOPIE_CFLAGS ??= "" CCACHE_DISABLE ?= "1" def go_map_arch(a, d): - import re - if re.match('i.86', a): - return '386' - elif a == 'x86_64': - return 'amd64' - elif re.match('arm.*', a): - return 'arm' - elif re.match('aarch64.*', a): - return 'arm64' - elif re.match('mips64el.*', a): - return 'mips64le' - elif re.match('mips64.*', a): - return 'mips64' - elif a == 'mips': - return 'mips' - elif a == 'mipsel': - return 'mipsle' - elif re.match('p(pc|owerpc)(64le)', a): - return 'ppc64le' - elif re.match('p(pc|owerpc)(64)', a): - return 'ppc64' - elif a == 'riscv64': - return 'riscv64' - else: + arch = oe.go.map_arch(a) + if not arch: raise bb.parse.SkipRecipe("Unsupported CPU architecture: %s" % a) + return arch def go_map_arm(a, d): if a.startswith("arm"):
meta/lib/oe/go.py new file +32 -0
@@ -0,0 +1,32 @@ +# +# Copyright OpenEmbedded Contributors +# +# SPDX-License-Identifier: MIT +# + +import re + +def map_arch(a): + if re.match('i.86', a): + return '386' + elif a == 'x86_64': + return 'amd64' + elif re.match('arm.*', a): + return 'arm' + elif re.match('aarch64.*', a): + return 'arm64' + elif re.match('mips64el.*', a): + return 'mips64le' + elif re.match('mips64.*', a): + return 'mips64' + elif a == 'mips': + return 'mips' + elif a == 'mipsel': + return 'mipsle' + elif re.match('p(pc|owerpc)(64le)', a): + return 'ppc64le' + elif re.match('p(pc|owerpc)(64)', a): + return 'ppc64' + elif a == 'riscv64': + return 'riscv64' + return ''
Signature · 1 line
2.34.1
PATCH 16/16 libxcrypt: fixed some build error for nativesdk with mingw
In reply to Steve SakomanFrom: Wenlin Kang <[email protected]>
Steps to reproduce
1) add layer meta-mingw
2) add line in local.conf
SDKMACHINE = "x86_64-mingw32"
3) bitbake nativesdk-libxcrypt
Fixed:
1. .symver error
| {standard input}: Assembler messages:
| {standard input}:4: Error: unknown pseudo-op: `.symver'
2. pedantic error
| ../git/lib/crypt.c:316:24: error: ISO C does not allow extra ';' outside of a function [-Werror=pedantic] | 316 | SYMVER_crypt_gensalt_rn; | |
3. conversion error
| ../git/lib/util-get-random-bytes.c: In function '_crypt_get_random_bytes':
| ../git/lib/util-get-random-bytes.c:140:42: error: conversion from 'size_t' {aka 'long long unsigned int'} to 'unsigned int' may change value [-Werror=conversion]
| 140 | ssize_t nread = read (fd, buf, buflen);--- .../0001-Fix-for-compilation-on-Windows.patch | 37 +++++++++++++++ ...dom-bytes.c-fixed-conversion-error-w.patch | 47 +++++++++++++++++++ meta/recipes-core/libxcrypt/libxcrypt.inc | 4 ++ 3 files changed, 88 insertions(+) create mode 100644 meta/recipes-core/libxcrypt/files/0001-Fix-for-compilation-on-Windows.patch create mode 100644 meta/recipes-core/libxcrypt/files/0001-lib-util-get-random-bytes.c-fixed-conversion-error-w.patch
meta/recipes-core/libxcrypt/files/0001-Fix-for-compilation-on-Windows.patch new file +37 -0
@@ -0,0 +1,37 @@ +From a507b628a5a5d4e4f1cf0f0a9a72967470ee7624 Mon Sep 17 00:00:00 2001 +From: Brecht Sanders <[email protected]> +Date: Fri, 3 Feb 2023 08:44:49 +0100 +Subject: [PATCH] Fix for compilation on Windows + +This fix allows the library to build on Windows (at least with MinGW-w64). + +`.symver` is only supported for ELF format but Windows uses COFF/PE. + +Workaround dummy define of `symver_set()` + +Upstream-Status: Backport [https://github.com/besser82/libxcrypt/commit/a507b628a5a5d4e4f1cf0f0a9a72967470ee7624] + +Signed-off-by: Wenlin Kang <[email protected]> +--- + lib/crypt-port.h | 5 +++++ + 1 file changed, 5 insertions(+) + +diff --git a/lib/crypt-port.h b/lib/crypt-port.h +index f06ca24..a707939 100644 +--- a/lib/crypt-port.h ++++ b/lib/crypt-port.h +@@ -201,6 +201,11 @@ extern size_t strcpy_or_abort (void *dst, size_t d_size, const void *src); + __asm__(".globl _" extstr); \ + __asm__(".set _" extstr ", _" #intname) + ++#elif defined _WIN32 ++ ++/* .symver is only supported for ELF format, Windows uses COFF/PE */ ++# define symver_set(extstr, intname, version, mode) ++ + #elif defined __GNUC__ && __GNUC__ >= 3 + + # define _strong_alias(name, aliasname) \ +-- +2.34.1 +
meta/recipes-core/libxcrypt/files/0001-lib-util-get-random-bytes.c-fixed-conversion-error-w.patch new file +47 -0
47 lines not on this page · raw message
meta/recipes-core/libxcrypt/libxcrypt.inc +4 -0
@@ -16,6 +16,8 @@ SRCBRANCH ?= "master" SRC_URI += "file://fix_cflags_handling.patch \ file://0001-Make-BuildCommon.pm-compatible-with-latest-perl.patch \ file://0002-Remove-smartmatch-usage-from-gen-crypt-h.patch \ + file://0001-Fix-for-compilation-on-Windows.patch \ + file://0001-lib-util-get-random-bytes.c-fixed-conversion-error-w.patch \ " PROVIDES = "virtual/crypt"
@@ -29,4 +31,6 @@ CPPFLAGS:append:class-nativesdk = " -Wno-error" API = "--disable-obsolete-api" EXTRA_OECONF += "${API}" +CFLAGS:append:class-nativesdk = " -Wno-pedantic" + BBCLASSEXTEND = "native nativesdk"
Signature · 1 line
2.34.1
Re: [OE-core][kirkstone 16/16] libxcrypt: fixed some build error for nativesdk with mingw
Quoted 25 lines · Steve Sakoman
From: Wenlin Kang <[email protected]>
Steps to reproduce
1) add layer meta-mingw
2) add line in local.confSDKMACHINE = "x86_64-mingw32"3) bitbake nativesdk-libxcrypt
Fixed:
1. .symver error
| {standard input}: Assembler messages:
| {standard input}:4: Error: unknown pseudo-op: `.symver'2. pedantic error
| ../git/lib/crypt.c:316:24: error: ISO C does not allow extra ';' outside of a function [-Werror=pedantic] | 316 | SYMVER_crypt_gensalt_rn; | |3. conversion error
| ../git/lib/util-get-random-bytes.c: In function '_crypt_get_random_bytes': | ../git/lib/util-get-random-bytes.c:140:42: error: conversion from 'size_t' {aka 'long long unsigned int'} to 'unsigned int' may change value [-Werror=conversion] | 140 | ssize_t nread = read (fd, buf, buflen);Signed-off-by Wenlin Kang <[email protected]>Signed-off-by Steve Sakoman <[email protected]>
Quoted 7 lines
--- .../0001-Fix-for-compilation-on-Windows.patch | 37 +++++++++++++++ ...dom-bytes.c-fixed-conversion-error-w.patch | 47 +++++++++++++++++++ meta/recipes-core/libxcrypt/libxcrypt.inc | 4 ++ 3 files changed, 88 insertions(+) create mode 100644 meta/recipes-core/libxcrypt/files/0001-Fix-for-compilation-on-Windows.patch create mode 100644 meta/recipes-core/libxcrypt/files/0001-lib-util-get-random-bytes.c-fixed-conversion-error-w.patch
This isn't in master, not is it going to be.
Cheers,
Richard
Re: [OE-core][kirkstone 15/16] goarch: Move Go architecture mapping to a library
In reply to Steve SakomanQuoted 25 lines · Steve Sakoman
From: Peter Marko <[email protected]>
Other spaces uses the Go architecture definitions as their own (for example, container arches are defined to be Go arches). To make it easier for other places to use this mapping, move the code that does the translation of OpenEmbedded arches to Go arches to a library.
(From oe-core rev:
3e86f72fc2e1cc2e5ea4b4499722d736941167ce)This commit together with meta-virtualization commit
115f6367f37095415f289fb6981cda9608ac72ffbroke meta-virtualization master used with meta-lts-mixins kirkstone/go which is our primary usecase for having kirkstone/go mixin layerManually crafted since cherry-pick had too many conflicts:
* different path to classes
* additional architecture loongarch64
* different way how to import librarySigned-off-by Peter Marko <[email protected]>Cc Joshua Watt <[email protected]>Cc Bruce Ashfield <[email protected]>Cc Jose Quaresma <[email protected]>Signed-off-by Steve Sakoman <[email protected]>
Quoted 6 lines
--- meta/classes/base.bbclass | 2 +- meta/classes/goarch.bbclass | 27 +++------------------------ meta/lib/oe/go.py | 32 ++++++++++++++++++++++++++++++++ 3 files changed, 36 insertions(+), 25 deletions(-) create mode 100644 meta/lib/oe/go.py
This did cause problems for some layers such as meta-virtualization so I'd want to check those layers are ok with this?
Cheers,
Richard
Re: [OE-core][kirkstone 09/16] binutils: Fix CVE-2022-47007
In reply to Steve SakomanQuoted 35 lines · Steve Sakoman
From: Deepthi Hemraj <[email protected]>
Signed-off-by Deepthi Hemraj <[email protected]>Signed-off-by Steve Sakoman <[email protected]>--- .../binutils/binutils-2.38.inc | 1 + .../binutils/0033-CVE-2022-47007.patch | 34 +++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patchmeta/recipes-devtools/binutils/binutils-2.38.inc +1
-0@@ -67,5 +67,6 @@ SRC_URI = "\ file://0031-CVE-2022-47695.patch \ file://CVE-2022-48063.patch \ file://0032-CVE-2022-47010.patch \ + file://0033-CVE-2022-47007.patch \ " S = "${WORKDIR}/git"meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch new file +8
-0@@ -0,0 +1,34 @@ +From: Alan Modra <[email protected]> +Date: Thu, 16 Jun 2022 23:30:41 +0000 (+0930) +Subject: PR29254, memory leak in stab_demangle_v3_arg +X-Git-Tag: binutils-2_39~237 +X-Git-Url: https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=0ebc886149c22aceaf8ed74267821a59ca9d03eb + +PR29254, memory leak in stab_demangle_v3_arg +
meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch line 18
Quoted 10 lines
meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch new file +10
-0+ PR 29254 + * stabs.c (stab_demangle_v3_arg): Free dt on failure path. + +Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=0ebc886149c22aceaf8ed74267821a59ca9d03eb] + +CVE: CVE-2022-47007 + +Signed-off-by: Deepthi Hemraj <[email protected]> +--- +
This has not merged to master yet. It probably will but...
Cheers,
Richard
Re: [OE-core][kirkstone 15/16] goarch: Move Go architecture mapping to a library
In reply to Richard PurdieQuoted 34 lines · Richard Purdie
Quoted 25 lines · Steve Sakoman
From: Peter Marko <[email protected]>
Other spaces uses the Go architecture definitions as their own (for example, container arches are defined to be Go arches). To make it easier for other places to use this mapping, move the code that does the translation of OpenEmbedded arches to Go arches to a library.
(From oe-core rev:
3e86f72fc2e1cc2e5ea4b4499722d736941167ce)This commit together with meta-virtualization commit
115f6367f37095415f289fb6981cda9608ac72ffbroke meta-virtualization master used with meta-lts-mixins kirkstone/go which is our primary usecase for having kirkstone/go mixin layerManually crafted since cherry-pick had too many conflicts:
* different path to classes
* additional architecture loongarch64
* different way how to import librarySigned-off-by Peter Marko <[email protected]>Cc Joshua Watt <[email protected]>Cc Bruce Ashfield <[email protected]>Cc Jose Quaresma <[email protected]>Signed-off-by Steve Sakoman <[email protected]>Quoted 6 lines
--- meta/classes/base.bbclass | 2 +- meta/classes/goarch.bbclass | 27 +++------------------------ meta/lib/oe/go.py | 32 ++++++++++++++++++++++++++++++++ 3 files changed, 36 insertions(+), 25 deletions(-) create mode 100644 meta/lib/oe/go.py
Quoted 3 lines
This did cause problems for some layers such as meta-virtualization so I'd want to check those layers are ok with this?
It should be fine, the issues were around it not being present and recipes trying to use the mapping directly without the go.bbclass being inherited.
It won't be used in kirkstone, so is a no-op there (for meta-virt), but that does mean some mixin and multi release compatible layers can more easily to backports.
Bruce
Quoted 12 lines
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#191144): https://lists.openembedded.org/g/openembedded-core/message/191144
Mute This Topic: https://lists.openembedded.org/mt/102742416/1050810
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
Re: [OE-core][kirkstone 16/16] libxcrypt: fixed some build error for nativesdk with mingw
In reply to Richard PurdieQuoted 35 lines · Richard Purdie
Quoted 25 lines · Steve Sakoman
From: Wenlin Kang <[email protected]>
Steps to reproduce
1) add layer meta-mingw
2) add line in local.confSDKMACHINE = "x86_64-mingw32"3) bitbake nativesdk-libxcrypt
Fixed:
1. .symver error
| {standard input}: Assembler messages:
| {standard input}:4: Error: unknown pseudo-op: `.symver'2. pedantic error
| ../git/lib/crypt.c:316:24: error: ISO C does not allow extra ';' outside of a function [-Werror=pedantic] | 316 | SYMVER_crypt_gensalt_rn; | |3. conversion error
| ../git/lib/util-get-random-bytes.c: In function '_crypt_get_random_bytes': | ../git/lib/util-get-random-bytes.c:140:42: error: conversion from 'size_t' {aka 'long long unsigned int'} to 'unsigned int' may change value [-Werror=conversion] | 140 | ssize_t nread = read (fd, buf, buflen);Signed-off-by Wenlin Kang <[email protected]>Signed-off-by Steve Sakoman <[email protected]>Quoted 7 lines
--- .../0001-Fix-for-compilation-on-Windows.patch | 37 +++++++++++++++ ...dom-bytes.c-fixed-conversion-error-w.patch | 47 +++++++++++++++++++ meta/recipes-core/libxcrypt/libxcrypt.inc | 4 ++ 3 files changed, 88 insertions(+) create mode 100644 meta/recipes-core/libxcrypt/files/0001-Fix-for-compilation-on-Windows.patch create mode 100644 meta/recipes-core/libxcrypt/files/0001-lib-util-get-random-bytes.c-fixed-conversion-error-w.patch
Quoted 1 line
This isn't in master, not is it going to be.
OK, I will drop this patch for kirkstone. Thanks for the review.
Steve
Re: [OE-core][kirkstone 09/16] binutils: Fix CVE-2022-47007
In reply to Richard PurdieQuoted 41 lines · Richard Purdie
Quoted 39 lines · Steve Sakoman
From: Deepthi Hemraj <[email protected]>
Signed-off-by Deepthi Hemraj <[email protected]>Signed-off-by Steve Sakoman <[email protected]>--- .../binutils/binutils-2.38.inc | 1 + .../binutils/0033-CVE-2022-47007.patch | 34 +++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patchmeta/recipes-devtools/binutils/binutils-2.38.inc +1
-0@@ -67,5 +67,6 @@ SRC_URI = "\ file://0031-CVE-2022-47695.patch \ file://CVE-2022-48063.patch \ file://0032-CVE-2022-47010.patch \ + file://0033-CVE-2022-47007.patch \ " S = "${WORKDIR}/git"meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch new file +12
-0@@ -0,0 +1,34 @@ +From: Alan Modra <[email protected]> +Date: Thu, 16 Jun 2022 23:30:41 +0000 (+0930) +Subject: PR29254, memory leak in stab_demangle_v3_arg +X-Git-Tag: binutils-2_39~237 +X-Git-Url: https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=0ebc886149c22aceaf8ed74267821a59ca9d03eb + +PR29254, memory leak in stab_demangle_v3_arg + + PR 29254 + * stabs.c (stab_demangle_v3_arg): Free dt on failure path. + +Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=0ebc886149c22aceaf8ed74267821a59ca9d03eb]
Quoted 8 lines
meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch line 18
Quoted 6 lines
meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch new file +6
-0+ +CVE: CVE-2022-47007 + +Signed-off-by: Deepthi Hemraj <[email protected]> +--- +This has not merged to master yet. It probably will but...
This CVE shouldn't affect master, it is for binutils versions 2.34 thru 2.38, while master is 2.41
See: https://nvd.nist.gov/vuln/detail/CVE-2022-47007
Steve
Re: [OE-core][kirkstone 15/16] goarch: Move Go architecture mapping to a library
In reply to Bruce AshfieldQuoted 41 lines · Bruce Ashfield
Quoted 34 lines · Richard Purdie
Quoted 25 lines · Steve Sakoman
From: Peter Marko <[email protected]>
Other spaces uses the Go architecture definitions as their own (for example, container arches are defined to be Go arches). To make it easier for other places to use this mapping, move the code that does the translation of OpenEmbedded arches to Go arches to a library.
(From oe-core rev:
3e86f72fc2e1cc2e5ea4b4499722d736941167ce)This commit together with meta-virtualization commit
115f6367f37095415f289fb6981cda9608ac72ffbroke meta-virtualization master used with meta-lts-mixins kirkstone/go which is our primary usecase for having kirkstone/go mixin layerManually crafted since cherry-pick had too many conflicts:
* different path to classes
* additional architecture loongarch64
* different way how to import librarySigned-off-by Peter Marko <[email protected]>Cc Joshua Watt <[email protected]>Cc Bruce Ashfield <[email protected]>Cc Jose Quaresma <[email protected]>Signed-off-by Steve Sakoman <[email protected]>Quoted 6 lines
--- meta/classes/base.bbclass | 2 +- meta/classes/goarch.bbclass | 27 +++------------------------ meta/lib/oe/go.py | 32 ++++++++++++++++++++++++++++++++ 3 files changed, 36 insertions(+), 25 deletions(-) create mode 100644 meta/lib/oe/go.pyQuoted 3 lines
This did cause problems for some layers such as meta-virtualization so I'd want to check those layers are ok with this?
Quoted 6 lines
It should be fine, the issues were around it not being present and recipes trying to use the mapping directly without the go.bbclass being inherited.
It won't be used in kirkstone, so is a no-op there (for meta-virt), but that does mean some mixin and multi release compatible layers can more easily to backports.
Thanks for reviewing Richard and Bruce!
Since Bruce confirms there are no issues with meta-virt I'll leave this in the series.
Steve
Re: [OE-core][kirkstone 09/16] binutils: Fix CVE-2022-47007
In reply to Steve SakomanQuoted 52 lines · Steve Sakoman
Quoted 41 lines · Richard Purdie
Quoted 39 lines · Steve Sakoman
From: Deepthi Hemraj <[email protected]>
Signed-off-by Deepthi Hemraj <[email protected]>Signed-off-by Steve Sakoman <[email protected]>--- .../binutils/binutils-2.38.inc | 1 + .../binutils/0033-CVE-2022-47007.patch | 34 +++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patchmeta/recipes-devtools/binutils/binutils-2.38.inc +1
-0@@ -67,5 +67,6 @@ SRC_URI = "\ file://0031-CVE-2022-47695.patch \ file://CVE-2022-48063.patch \ file://0032-CVE-2022-47010.patch \ + file://0033-CVE-2022-47007.patch \ " S = "${WORKDIR}/git"meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch new file +12
-0@@ -0,0 +1,34 @@ +From: Alan Modra <[email protected]> +Date: Thu, 16 Jun 2022 23:30:41 +0000 (+0930) +Subject: PR29254, memory leak in stab_demangle_v3_arg +X-Git-Tag: binutils-2_39~237 +X-Git-Url: https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=0ebc886149c22aceaf8ed74267821a59ca9d03eb + +PR29254, memory leak in stab_demangle_v3_arg + + PR 29254 + * stabs.c (stab_demangle_v3_arg): Free dt on failure path. + +Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=0ebc886149c22aceaf8ed74267821a59ca9d03eb]Quoted 8 lines
meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch line 18
Quoted 6 lines
meta/recipes-devtools/binutils/binutils/0033-CVE-2022-47007.patch new file +6
-0+ +CVE: CVE-2022-47007 + +Signed-off-by: Deepthi Hemraj <[email protected]> +--- +This has not merged to master yet. It probably will but...
Quoted 4 lines
This CVE shouldn't affect master, it is for binutils versions 2.34 thru 2.38, while master is 2.41
This was merged to master but clearly shouldn't be as it was reverted upstream as part of:
Cheers,
Richard