Patch review
cover Patch review
Please review this set of changes for whinlatter and have comments back by end of day Monday, March 9.
Passed a-full on autobuilder with warnings:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3334
The sub-build qemux86-64-ptest had a ptest failure
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3207
It is a known AB-INT bug: 15718 – AB-INT: gstreamer ptest never ending (Bitbake still alive)
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15718
This is not related to this series.
The following changes since commit 45cba1329d541fdc5857d6df2624b34c91133f7a:
build-appliance-image: Update to whinlatter head revisions (2026-02-27 17:46:44 +0000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/whinlatter-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/whinlatter-nut
Adarsh Jagadish Kamini (1):
python3-pip: Backport fix CVE-2026-1703
Ankur Tyagi (1):
wireless-regdb: upgrade 2025.10.07 -> 2026.02.04
Antonin Godard (1):
python3: skip flaky test_default_timeout test
Hugo SIMELIERE (2):
zlib: Fix CVE-2026-27171
harfbuzz: Fix CVE-2026-22693
Peter Marko (3):
linux-yocto: apply cve-exclusions also to rt and tiny recipe variants
cve-exclusions: set status for 5 CVEs
ffmpeg: set status for CVE-2025-12343
Shaik Moin (1):
gdk-pixbuf: Fix CVE-2025-6199
Vijay Anusuri (1):
gnutls: Fix CVE-2025-14831
Yoann Congal (2):
README: Add whinlatter subject-prefix to git-send-email suggestion
b4-config: add send-prefixes for whinlatter
.b4-config | 1 +
README.OE-Core.md | 2 +-
.../zlib/zlib/CVE-2026-27171.patch | 63 +++
meta/recipes-core/zlib/zlib_1.3.1.bb | 1 +
.../python/python3-pip/CVE-2026-1703.patch | 41 ++
.../python/python3-pip_25.2.bb | 4 +-
...kip-flaky-test_default_timeout-tests.patch | 49 ++
.../python/python3_3.13.11.bb | 1 +
.../gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch | 36 ++
.../gdk-pixbuf/gdk-pixbuf_2.42.12.bb | 1 +
.../harfbuzz/files/CVE-2026-22693.patch | 33 ++
.../harfbuzz/harfbuzz_11.4.5.bb | 4 +-
meta/recipes-kernel/linux/cve-exclusion.inc | 16 +
.../linux/linux-yocto-rt_6.12.bb | 1 +
.../linux/linux-yocto-rt_6.16.bb | 1 +
.../linux/linux-yocto-tiny_6.12.bb | 1 +
.../linux/linux-yocto-tiny_6.16.bb | 1 +
....10.07.bb => wireless-regdb_2026.02.04.bb} | 2 +-
meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.bb | 1 +
.../gnutls/gnutls/CVE-2025-14831-1.patch | 119 +++++
.../gnutls/gnutls/CVE-2025-14831-10.patch | 424 +++++++++++++++
.../gnutls/gnutls/CVE-2025-14831-2.patch | 66 +++
.../gnutls/gnutls/CVE-2025-14831-3.patch | 30 ++
.../gnutls/gnutls/CVE-2025-14831-4.patch | 45 ++
.../gnutls/gnutls/CVE-2025-14831-5.patch | 205 +++++++
.../gnutls/gnutls/CVE-2025-14831-6.patch | 505 ++++++++++++++++++
.../gnutls/gnutls/CVE-2025-14831-7.patch | 124 +++++
.../gnutls/gnutls/CVE-2025-14831-8.patch | 155 ++++++
.../gnutls/gnutls/CVE-2025-14831-9.patch | 110 ++++
meta/recipes-support/gnutls/gnutls_3.8.10.bb | 10 +
30 files changed, 2048 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-core/zlib/zlib/CVE-2026-27171.patch
create mode 100644 meta/recipes-devtools/python/python3-pip/CVE-2026-1703.patch
create mode 100644 meta/recipes-devtools/python/python3/0001-Skip-flaky-test_default_timeout-tests.patch
create mode 100644 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch
create mode 100644 meta/recipes-graphics/harfbuzz/files/CVE-2026-22693.patch
rename meta/recipes-kernel/wireless-regdb/{wireless-regdb_2025.10.07.bb => wireless-regdb_2026.02.04.bb} (94%)
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-1.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-10.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-2.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-3.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-4.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-5.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-6.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-7.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-8.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-9.patchPATCH 1/12 python3-pip: Backport fix CVE-2026-1703
From: Adarsh Jagadish Kamini <[email protected]>
Include the patch linked in the NVD report: https://github.com/pypa/pip/commit/8e227a9be4faa9594e05d02ca05a413a2a4e7735
--- .../python/python3-pip/CVE-2026-1703.patch | 41 +++++++++++++++++++ .../python/python3-pip_25.2.bb | 4 +- 2 files changed, 44 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-devtools/python/python3-pip/CVE-2026-1703.patch
meta/recipes-devtools/python/python3-pip/CVE-2026-1703.patch new file +41 -0
@@ -0,0 +1,41 @@ +From abce61e230c47598ce836157d075608595216a4c Mon Sep 17 00:00:00 2001 +From: Damian Shaw <[email protected]> +Date: Fri, 30 Jan 2026 16:27:57 -0500 +Subject: [PATCH v4] Merge pull request #13777 from sethmlarson/commonpath + +Use os.path.commonpath() instead of commonprefix() + +CVE: CVE-2026-1703 + +Upstream-Status: Backport [https://github.com/pypa/pip/commit/8e227a9be4faa9594e05d02ca05a413a2a4e7735] + +Signed-off-by: Adarsh Jagadish Kamini <[email protected]> +--- + news/+1ee322a1.bugfix.rst | 1 + + src/pip/_internal/utils/unpacking.py | 2 +- + 2 files changed, 2 insertions(+), 1 deletion(-) + create mode 100644 news/+1ee322a1.bugfix.rst + +diff --git a/news/+1ee322a1.bugfix.rst b/news/+1ee322a1.bugfix.rst +new file mode 100644 +index 000000000..edb1b320c +--- /dev/null ++++ b/news/+1ee322a1.bugfix.rst +@@ -0,0 +1 @@ ++Use a path-segment prefix comparison, not char-by-char. +diff --git a/src/pip/_internal/utils/unpacking.py b/src/pip/_internal/utils/unpacking.py +index 0ad3129ac..7cb3de3c4 100644 +--- a/src/pip/_internal/utils/unpacking.py ++++ b/src/pip/_internal/utils/unpacking.py +@@ -83,7 +83,7 @@ def is_within_directory(directory: str, target: str) -> bool: + abs_directory = os.path.abspath(directory) + abs_target = os.path.abspath(target) + +- prefix = os.path.commonprefix([abs_directory, abs_target]) ++ prefix = os.path.commonpath([abs_directory, abs_target]) + return prefix == abs_directory + + +-- +2.34.1 +
meta/recipes-devtools/python/python3-pip_25.2.bb +3 -1
@@ -24,7 +24,9 @@ LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=63ec52baf95163b597008bb46db68030 \ inherit pypi python_setuptools_build_meta -SRC_URI += "file://no_shebang_mangling.patch" +SRC_URI += "file://no_shebang_mangling.patch \ + file://CVE-2026-1703.patch \ + " SRC_URI[sha256sum] = "578283f006390f85bb6282dffb876454593d637f5d1be494b5202ce4877e71f2"
PATCH 2/12 wireless-regdb: upgrade 2025.10.07 -> 2026.02.04
In reply to Yoann CongalFrom: Ankur Tyagi <[email protected]>
---
...ireless-regdb_2025.10.07.bb => wireless-regdb_2026.02.04.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-kernel/wireless-regdb/{wireless-regdb_2025.10.07.bb => wireless-regdb_2026.02.04.bb} (94%)meta/recipes-kernel/wireless-regdb/wireless-regdb_2026.02.04.bb renamed from meta/recipes-kernel/wireless-regdb/wireless-regdb_2025.10.07.bb +1 -1
@@ -5,7 +5,7 @@ LICENSE = "ISC" LIC_FILES_CHKSUM = "file://LICENSE;md5=07c4f6dea3845b02a18dc00c8c87699c" SRC_URI = "https://www.kernel.org/pub/software/network/${BPN}/${BP}.tar.xz" -SRC_URI[sha256sum] = "d4c872a44154604c869f5851f7d21d818d492835d370af7f58de8847973801c3" +SRC_URI[sha256sum] = "0ff48a5cd9e9cfe8e815a24e023734919e9a3b7ad2f039243ad121cf5aabf6c6" inherit bin_package allarch
PATCH 3/12 gdk-pixbuf: Fix CVE-2025-6199
In reply to Yoann CongalFrom: Shaik Moin <[email protected]>
Backport the fix for CVE-2025-6199
Add below patch to fix
CVE-2025-6199.patch
Reference: In Ubuntu and debian, fixed patch is given -> [https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/commit/c4986342b241cdc075259565f3fa7a7597d32a32]
--- .../gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch | 36 +++++++++++++++++++ .../gdk-pixbuf/gdk-pixbuf_2.42.12.bb | 1 + 2 files changed, 37 insertions(+) create mode 100644 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch new file +36 -0
@@ -0,0 +1,36 @@ +From 140200be0b4d5355aab76a6fd474e17d117045ca Mon Sep 17 00:00:00 2001 +From: lumi <[email protected]> +Date: Sat, 7 Jun 2025 22:27:06 +0200 +Subject: [PATCH] lzw: Fix reporting of bytes written in decoder + +When the LZW decoder encounters an invalid code, it stops +processing the image and returns the whole buffer size. +It should return the amount of bytes written, instead. + +Fixes #257 + +CVE: CVE-2025-6199 + +Upstream-Status: Backport [https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/commit/c4986342b241cdc075259565f3fa7a7597d32a32] + +Signed-off-by: Shaik Moin <[email protected]> +--- + gdk-pixbuf/lzw.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/gdk-pixbuf/lzw.c b/gdk-pixbuf/lzw.c +index 15293560b..4f3dd8beb 100644 +--- a/gdk-pixbuf/lzw.c ++++ b/gdk-pixbuf/lzw.c +@@ -208,7 +208,7 @@ lzw_decoder_feed (LZWDecoder *self, + /* Invalid code received - just stop here */ + if (self->code >= self->code_table_size) { + self->last_code = self->eoi_code; +- return output_length; ++ return n_written; + } + + /* Convert codeword into indexes */ +-- +2.34.1 +
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.42.12.bb +1 -0
@@ -22,6 +22,7 @@ SRC_URI += "\ file://run-ptest \ file://fatal-loader.patch \ file://0001-meson.build-allow-a-subset-of-tests-in-cross-compile.patch \ + file://CVE-2025-6199.patch \ " GIR_MESON_OPTION = 'introspection'
PATCH 4/12 linux-yocto: apply cve-exclusions also to rt and tiny recipe variants
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Version is the same as base kernel, only configuration differs. There is no reason to not apply the exclusions to all variants.
This commit is equivalent of master commit77fb0331ecc0cb9eff6a711c2a7889f2f6bdda92
--- meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb | 1 + meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb | 1 + meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb | 1 + meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb | 1 + 4 files changed, 4 insertions(+)
meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb +1 -0
@@ -3,6 +3,7 @@ KBRANCH ?= "v6.12/standard/preempt-rt/base" require recipes-kernel/linux/linux-yocto.inc # CVE exclusions +include recipes-kernel/linux/cve-exclusion.inc include recipes-kernel/linux/cve-exclusion_6.12.inc # Skip processing of this recipe if it is not explicitly specified as the
meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb +1 -0
@@ -3,6 +3,7 @@ KBRANCH ?= "v6.16/standard/preempt-rt/base" require recipes-kernel/linux/linux-yocto.inc # CVE exclusions +include recipes-kernel/linux/cve-exclusion.inc include recipes-kernel/linux/cve-exclusion_6.16.inc # Skip processing of this recipe if it is not explicitly specified as the
meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb +1 -0
@@ -6,6 +6,7 @@ KCONFIG_MODE = "--allnoconfig" require recipes-kernel/linux/linux-yocto.inc # CVE exclusions +include recipes-kernel/linux/cve-exclusion.inc include recipes-kernel/linux/cve-exclusion_6.12.inc LINUX_VERSION ?= "6.12.69"
meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb +1 -0
@@ -6,6 +6,7 @@ KCONFIG_MODE = "--allnoconfig" require recipes-kernel/linux/linux-yocto.inc # CVE exclusions +include recipes-kernel/linux/cve-exclusion.inc include recipes-kernel/linux/cve-exclusion_6.16.inc LINUX_VERSION ?= "6.16.11"
PATCH 5/12 cve-exclusions: set status for 5 CVEs
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Reuse work of Debian researchers and set status for fixed CVEs accordingly.
These are not tracked by kernel itself, so generated exclusions won't help here.
* https://security-tracker.debian.org/tracker/CVE-2022-38096
* https://security-tracker.debian.org/tracker/CVE-2023-39176
* https://security-tracker.debian.org/tracker/CVE-2023-39179
* https://security-tracker.debian.org/tracker/CVE-2023-39180
* https://security-tracker.debian.org/tracker/CVE-2023-6535
(From OE-Core rev: 699dbbdf3ab2693bae8a7e0425e2519250fdfec4)
--- meta/recipes-kernel/linux/cve-exclusion.inc | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
meta/recipes-kernel/linux/cve-exclusion.inc +16 -0
@@ -157,3 +157,19 @@ CVE_STATUS[CVE-2023-7042] = "fixed-version: Fixed from 6.9rc1" #Fix https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7315dc1e122c85ffdfc8defffbb8f8b616c2eb1a CVE_STATUS[CVE-2024-0193] = "fixed-version: Fixed from 6.7" + +# Fix https://git.kernel.org/linus/517621b7060096e48e42f545fa6646fc00252eac +CVE_STATUS[CVE-2022-38096] = "fixed-version: Fixed from 6.9" + +# Fix https://git.kernel.org/linus/5aa4fda5aa9c2a5a7bac67b4a12b089ab81fee3c +# Fix https://git.kernel.org/linus/79ed288cef201f1f212dfb934bcaac75572fb8f6 +CVE_STATUS[CVE-2023-39176] = "fixed-version: Fixed from 6.5" + +# Fix https://git.kernel.org/linus/e202a1e8634b186da38cbbff85382ea2b9e297cf +CVE_STATUS[CVE-2023-39179] = "fixed-version: Fixed from 6.5" +CVE_STATUS[CVE-2023-39180] = "fixed-version: Fixed from 6.5" + +# Fix https://git.kernel.org/linus/efa56305908ba20de2104f1b8508c6a7401833be +# Fix https://git.kernel.org/linus/0849a5441358cef02586fb2d60f707c0db195628 +# Fix https://git.kernel.org/linus/9a1abc24850eb759e36a2f8869161c3b7254c904 +CVE_STATUS[CVE-2023-6535] = "fixed-version: Fixed from 6.8"
PATCH 6/12 ffmpeg: set status for CVE-2025-12343
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Per [1] is patch for this CVE [2].
This is equivalent of [3] which is included in n8.0.
[1] https://security-tracker.debian.org/tracker/CVE-2025-12343
[2] https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/b8d5f65b9e89d893f27cf00799dbc15fc0ca2f8e
[3] https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/263e819aa45cd3c48bf6887be02b4ec504c02048
--- meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.bb | 1 + 1 file changed, 1 insertion(+)
meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.bb +1 -0
@@ -177,3 +177,4 @@ CVE_STATUS_WRONG_CPE[status] = "fixed-version: these CVEs are fixed in used vers CVE_STATUS[CVE-2025-25468] = "fixed-version: these CVEs are fixed since v8.0" CVE_STATUS[CVE-2025-25469] = "fixed-version: these CVEs are fixed since v8.0" +CVE_STATUS[CVE-2025-12343] = "fixed-version: this CVE are fixed since v8.0"
PATCH 7/12 zlib: Fix CVE-2026-27171
In reply to Yoann CongalFrom: Hugo SIMELIERE <[email protected]>
Pick patch from [1] also mentioned in [2]
[1] https://github.com/madler/zlib/issues/904
[2] https://security-tracker.debian.org/tracker/CVE-2026-27171
--- .../zlib/zlib/CVE-2026-27171.patch | 63 +++++++++++++++++++ meta/recipes-core/zlib/zlib_1.3.1.bb | 1 + 2 files changed, 64 insertions(+) create mode 100644 meta/recipes-core/zlib/zlib/CVE-2026-27171.patch
meta/recipes-core/zlib/zlib/CVE-2026-27171.patch new file +63 -0
@@ -0,0 +1,63 @@ +From f234bdf5c0f94b681312452fcd5e36968221fa04 Mon Sep 17 00:00:00 2001 +From: Mark Adler <[email protected]> +Date: Sun, 21 Dec 2025 18:17:56 -0800 +Subject: [PATCH] Check for negative lengths in crc32_combine functions. + +Though zlib.h says that len2 must be non-negative, this avoids the +possibility of an accidental infinite loop. + +Upstream-Status: Backport [https://github.com/madler/zlib/commit/ba829a458576d1ff0f26fc7230c6de816d1f6a77] +CVE: CVE-2026-27171 + +Signed-off-by: Hugo SIMELIERE <[email protected]> +--- + crc32.c | 4 ++++ + zlib.h | 4 ++-- + 2 files changed, 6 insertions(+), 2 deletions(-) + +diff --git a/crc32.c b/crc32.c +index 6c38f5c..33d8c79 100644 +--- a/crc32.c ++++ b/crc32.c +@@ -1019,6 +1019,8 @@ unsigned long ZEXPORT crc32(unsigned long crc, const unsigned char FAR *buf, + + /* ========================================================================= */ + uLong ZEXPORT crc32_combine64(uLong crc1, uLong crc2, z_off64_t len2) { ++ if (len2 < 0) ++ return 0; + #ifdef DYNAMIC_CRC_TABLE + once(&made, make_crc_table); + #endif /* DYNAMIC_CRC_TABLE */ +@@ -1032,6 +1034,8 @@ uLong ZEXPORT crc32_combine(uLong crc1, uLong crc2, z_off_t len2) { + + /* ========================================================================= */ + uLong ZEXPORT crc32_combine_gen64(z_off64_t len2) { ++ if (len2 < 0) ++ return 0; + #ifdef DYNAMIC_CRC_TABLE + once(&made, make_crc_table); + #endif /* DYNAMIC_CRC_TABLE */ +diff --git a/zlib.h b/zlib.h +index 8d4b932..8c7f8ac 100644 +--- a/zlib.h ++++ b/zlib.h +@@ -1758,14 +1758,14 @@ ZEXTERN uLong ZEXPORT crc32_combine(uLong crc1, uLong crc2, z_off_t len2); + seq1 and seq2 with lengths len1 and len2, CRC-32 check values were + calculated for each, crc1 and crc2. crc32_combine() returns the CRC-32 + check value of seq1 and seq2 concatenated, requiring only crc1, crc2, and +- len2. len2 must be non-negative. ++ len2. len2 must be non-negative, otherwise zero is returned. + */ + + /* + ZEXTERN uLong ZEXPORT crc32_combine_gen(z_off_t len2); + + Return the operator corresponding to length len2, to be used with +- crc32_combine_op(). len2 must be non-negative. ++ crc32_combine_op(). len2 must be non-negative, otherwise zero is returned. + */ + + ZEXTERN uLong ZEXPORT crc32_combine_op(uLong crc1, uLong crc2, uLong op); +-- +2.43.0 +
meta/recipes-core/zlib/zlib_1.3.1.bb +1 -0
@@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = "file://zlib.h;beginline=6;endline=23;md5=5377232268e952e9ef6 SRC_URI = "https://zlib.net/${BP}.tar.gz \ file://0001-configure-Pass-LDFLAGS-to-link-tests.patch \ file://run-ptest \ + file://CVE-2026-27171.patch \ " UPSTREAM_CHECK_URI = "http://zlib.net/"
PATCH 8/12 harfbuzz: Fix CVE-2026-22693
In reply to Yoann CongalFrom: Hugo SIMELIERE <[email protected]>
Pick patch mentioned in NVD report [1]
[1] https://nvd.nist.gov/vuln/detail/CVE-2026-22693
--- .../harfbuzz/files/CVE-2026-22693.patch | 33 +++++++++++++++++++ .../harfbuzz/harfbuzz_11.4.5.bb | 4 ++- 2 files changed, 36 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-graphics/harfbuzz/files/CVE-2026-22693.patch
meta/recipes-graphics/harfbuzz/files/CVE-2026-22693.patch new file +33 -0
@@ -0,0 +1,33 @@ +From 21c880d1154a5bcef2ef68c1687d286820a274ee Mon Sep 17 00:00:00 2001 +From: Behdad Esfahbod <[email protected]> +Date: Fri, 9 Jan 2026 04:54:42 -0700 +Subject: [PATCH] [cmap] malloc fail test (#5710) + +Fixes https://github.com/harfbuzz/harfbuzz/security/advisories/GHSA-xvjr-f2r9-c7ww + +Upstream-Status: Backport [https://github.com/harfbuzz/harfbuzz/commit/1265ff8d990284f04d8768f35b0e20ae5f60daae] +CVE: CVE-2026-22693 + +Signed-off-by: Hugo SIMELIERE <[email protected]> +--- + src/hb-ot-cmap-table.hh | 4 ++++ + 1 file changed, 4 insertions(+) + +diff --git a/src/hb-ot-cmap-table.hh b/src/hb-ot-cmap-table.hh +index 294b2b60d..95a436b54 100644 +--- a/src/hb-ot-cmap-table.hh ++++ b/src/hb-ot-cmap-table.hh +@@ -1679,6 +1679,10 @@ struct SubtableUnicodesCache { + { + SubtableUnicodesCache* cache = + (SubtableUnicodesCache*) hb_malloc (sizeof(SubtableUnicodesCache)); ++ ++ if (unlikely (!cache)) ++ return nullptr; ++ + new (cache) SubtableUnicodesCache (source_table); + return cache; + } +-- +2.43.0 +
meta/recipes-graphics/harfbuzz/harfbuzz_11.4.5.bb +3 -1
@@ -8,7 +8,9 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b98429b8e8e3c2a67cfef01e99e4893d \ file://src/hb-ucd.cc;beginline=1;endline=15;md5=29d4dcb6410429195df67efe3382d8bc \ " -SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BPN}-${PV}.tar.xz" +SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BPN}-${PV}.tar.xz \ + file://CVE-2026-22693.patch \ + " SRC_URI[sha256sum] = "0f052eb4ab01d8bae98ba971c954becb32be57d7250f18af343b1d27892e03fa" DEPENDS += "glib-2.0-native"
PATCH 9/12 gnutls: Fix CVE-2025-14831
In reply to Yoann CongalFrom: Vijay Anusuri <[email protected]>
Picked commits which mentions this CVE per [1].
[1] https://ubuntu.com/security/CVE-2025-14831
[2] https://security-tracker.debian.org/tracker/CVE-2025-14831
[3] https://gitlab.com/gnutls/gnutls/-/issues/1773
Backported
https://gitlab.com/gnutls/gnutls/-/commit/6e118a4dfe820ce62fc77130b89188bcd8fbcaad
to apply patches cleanly.
--- .../gnutls/gnutls/CVE-2025-14831-1.patch | 119 +++++ .../gnutls/gnutls/CVE-2025-14831-10.patch | 424 +++++++++++++++ .../gnutls/gnutls/CVE-2025-14831-2.patch | 66 +++ .../gnutls/gnutls/CVE-2025-14831-3.patch | 30 ++ .../gnutls/gnutls/CVE-2025-14831-4.patch | 45 ++ .../gnutls/gnutls/CVE-2025-14831-5.patch | 205 +++++++ .../gnutls/gnutls/CVE-2025-14831-6.patch | 505 ++++++++++++++++++ .../gnutls/gnutls/CVE-2025-14831-7.patch | 124 +++++ .../gnutls/gnutls/CVE-2025-14831-8.patch | 155 ++++++ .../gnutls/gnutls/CVE-2025-14831-9.patch | 110 ++++ meta/recipes-support/gnutls/gnutls_3.8.10.bb | 10 + 11 files changed, 1793 insertions(+) create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-1.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-10.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-2.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-3.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-4.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-5.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-6.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-7.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-8.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-9.patch
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-1.patch new file +119 -0
@@ -0,0 +1,119 @@ +From 6e118a4dfe820ce62fc77130b89188bcd8fbcaad Mon Sep 17 00:00:00 2001 +From: chenjianhu <[email protected]> +Date: Fri, 1 Aug 2025 17:18:23 +0800 +Subject: [PATCH] x509: fix incorrect handling in name constraints merging + +As mentioned in commit ca573d65 ("x509: Fix asymmetry in name +constraints intersection", 2016-07-29), the +_gnutls_name_constraints_intersect function exhibited an +asymmetry in name constraints intersection behavior, specifically +manifested as: +1. Nodes of unique types in PERMITTED (absent in PERMITTED2) were + preserved +2. Nodes of unique types in PERMITTED2 (absent in PERMITTED) were + discarded + +A 'used' flag was introduced, where if a node from PERMITTED2 was + not used for the intersection, it would be copied to PERMITTED. + +However,an unresolved edge case persisted: +- When 'removed.size > 0', the 'used' flag was unconditionally set +to 1 +- This prevented copying of PERMITTED2 nodes with unique types + +Signed-off-by: chenjianhu <[email protected]> +Modified-by: Daiki Ueno <[email protected]> + +Upstream-Status: Backport [https://gitlab.com/gnutls/gnutls/-/commit/6e118a4dfe820ce62fc77130b89188bcd8fbcaad] +CVE: CVE-2025-14831 #Backport to apply CVE patches cleanly +Signed-off-by: Vijay Anusuri <[email protected]> +--- + lib/x509/name_constraints.c | 5 +++- + tests/name-constraints-merge.c | 55 ++++++++++++++++++++++++++++++++++ + 2 files changed, 59 insertions(+), 1 deletion(-) + +diff --git a/lib/x509/name_constraints.c b/lib/x509/name_constraints.c +index 3c6e306303..2be6a2aaa6 100644 +--- a/lib/x509/name_constraints.c ++++ b/lib/x509/name_constraints.c +@@ -414,7 +414,10 @@ static int name_constraints_node_list_intersect( + gnutls_assert(); + goto cleanup; + } +- used = 1; ++ ++ if (t->type == t2->type) ++ used = 1; ++ + // if intersection is not empty + if (tmp != + NULL) { // intersection for this type is not empty +diff --git a/tests/name-constraints-merge.c b/tests/name-constraints-merge.c +index 03b3243cc7..70376aaa74 100644 +--- a/tests/name-constraints-merge.c ++++ b/tests/name-constraints-merge.c +@@ -418,6 +418,61 @@ void doit(void) + gnutls_x509_name_constraints_deinit(nc1); + gnutls_x509_name_constraints_deinit(nc2); + ++ /* 5: variant of suite 0: after moving rfc822Name (ccc.com) ++ * from NC1 to NC2, dNSName (xxx.ccc.com) should still be ++ * rejected. ++ * ++ * NC1: permitted DNS org ++ * permitted DNS ccc.com ++ * NC2: permitted DNS org ++ * permitted email ccc.com ++ * permitted DNS aaa.bbb.ccc.com ++ */ ++ suite = 5; ++ ++ ret = gnutls_x509_name_constraints_init(&nc1); ++ check_for_error(ret); ++ ++ ret = gnutls_x509_name_constraints_init(&nc2); ++ check_for_error(ret); ++ ++ set_name("org", &name); ++ ret = gnutls_x509_name_constraints_add_permitted( ++ nc1, GNUTLS_SAN_DNSNAME, &name); ++ check_for_error(ret); ++ ++ set_name("ccc.com", &name); ++ ret = gnutls_x509_name_constraints_add_permitted( ++ nc1, GNUTLS_SAN_DNSNAME, &name); ++ check_for_error(ret); ++ ++ set_name("org", &name); ++ ret = gnutls_x509_name_constraints_add_permitted( ++ nc2, GNUTLS_SAN_DNSNAME, &name); ++ check_for_error(ret); ++ ++ set_name("ccc.com", &name); ++ ret = gnutls_x509_name_constraints_add_permitted( ++ nc2, GNUTLS_SAN_RFC822NAME, &name); ++ check_for_error(ret); ++ ++ set_name("aaa.bbb.ccc.com", &name); ++ ret = gnutls_x509_name_constraints_add_permitted( ++ nc2, GNUTLS_SAN_DNSNAME, &name); ++ check_for_error(ret); ++ ++ ret = _gnutls_x509_name_constraints_merge(nc1, nc2); ++ check_for_error(ret); ++ ++ /* check intersection of permitted */ ++ set_name("xxx.ccc.com", &name); ++ ret = gnutls_x509_name_constraints_check(nc1, GNUTLS_SAN_DNSNAME, ++ &name); ++ check_test_result(suite, ret, NAME_REJECTED, &name); ++ ++ gnutls_x509_name_constraints_deinit(nc1); ++ gnutls_x509_name_constraints_deinit(nc2); ++ + /* Test footer */ + + if (debug) +-- +GitLab +
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-10.patch new file +424 -0
424 lines not on this page · raw message
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-2.patch new file +66 -0
66 lines not on this page · raw message
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-3.patch new file +30 -0
@@ -0,0 +1,30 @@ +From 85d6348a30c74d4ee3710e0f4652f634eaad6914 Mon Sep 17 00:00:00 2001 +From: Alexander Sosedkin <[email protected]> +Date: Mon, 26 Jan 2026 19:10:58 +0100 +Subject: [PATCH] tests/name-constraints-ip: stop swallowing errors... + +... now when it started to pass + +Signed-off-by: Alexander Sosedkin <[email protected]> + +Upstream-Status: Backport [https://gitlab.com/gnutls/gnutls/-/commit/85d6348a30c74d4ee3710e0f4652f634eaad6914] +CVE: CVE-2025-14831 +Signed-off-by: Vijay Anusuri <[email protected]> +--- + tests/name-constraints-ip.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/tests/name-constraints-ip.c b/tests/name-constraints-ip.c +index 7a196088dc..a0cf172b7f 100644 +--- a/tests/name-constraints-ip.c ++++ b/tests/name-constraints-ip.c +@@ -772,5 +772,5 @@ int main(int argc, char **argv) + cmocka_unit_test_setup_teardown( + check_ipv4v6_single_constraint_each, setup, teardown) + }; +- cmocka_run_group_tests(tests, NULL, NULL); ++ return cmocka_run_group_tests(tests, NULL, NULL); + } +-- +GitLab +
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-4.patch new file +45 -0
45 lines not on this page · raw message
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-5.patch new file +205 -0
205 lines not on this page · raw message
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-6.patch new file +505 -0
505 lines not on this page · raw message
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-7.patch new file +124 -0
124 lines not on this page · raw message
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-8.patch new file +155 -0
155 lines not on this page · raw message
meta/recipes-support/gnutls/gnutls/CVE-2025-14831-9.patch new file +110 -0
110 lines not on this page · raw message
meta/recipes-support/gnutls/gnutls_3.8.10.bb +10 -0
@@ -24,6 +24,16 @@ SRC_URI = "https://www.gnupg.org/ftp/gcrypt/gnutls/v${SHRT_VER}/gnutls-${PV}.tar file://run-ptest \ file://Add-ptest-support.patch \ file://CVE-2025-9820.patch \ + file://CVE-2025-14831-1.patch \ + file://CVE-2025-14831-2.patch \ + file://CVE-2025-14831-3.patch \ + file://CVE-2025-14831-4.patch \ + file://CVE-2025-14831-5.patch \ + file://CVE-2025-14831-6.patch \ + file://CVE-2025-14831-7.patch \ + file://CVE-2025-14831-8.patch \ + file://CVE-2025-14831-9.patch \ + file://CVE-2025-14831-10.patch \ " SRC_URI[sha256sum] = "db7fab7cce791e7727ebbef2334301c821d79a550ec55c9ef096b610b03eb6b7"
PATCH 10/12 README: Add whinlatter subject-prefix to git-send-email suggestion
In reply to Yoann CongalFrom: Yoann Congal <[email protected]>
That might help new users send correct first stable patches.
--- README.OE-Core.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
README.OE-Core.md +1 -1
@@ -22,7 +22,7 @@ As a quick guide, patches should be sent to [email protected] The git command to do that would be: ``` -git send-email -M -1 --to [email protected] +git send-email -M -1 --to [email protected] --subject-prefix='whinlatter][PATCH' ``` Mailing list:
PATCH 11/12 b4-config: add send-prefixes for whinlatter
In reply to Yoann CongalFrom: Yoann Congal <[email protected]>
That might help new users send correct first stable patches.
--- .b4-config | 1 + 1 file changed, 1 insertion(+)
.b4-config +1 -0
@@ -1,3 +1,4 @@ [b4] send-series-to = [email protected] prep-pre-flight-checks = disable-needs-auto-to-cc, disable-needs-checking + send-prefixes = whinlatter
Re: [OE-core][whinlatter 11/12] b4-config: add send-prefixes for whinlatter
Hi Yoann,
Quoted 3 lines · Yoann Congal via lists.openembedded.org
From: Yoann Congal <[email protected]>
That might help new users send correct first stable patches.
Also has the benefit of telling us against which tree they based their patch (for example long-EoL releases like we get every now and then). We should do this for all releases the moment it's branched off master.
Thanks!
Quentin
PATCH 12/12 python3: skip flaky test_default_timeout test
In reply to Yoann CongalFrom: Antonin Godard <[email protected]>
We have been observing intermittent issues with this test on the Autobuilder:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15885
This is probably due to the Autobuilder being heavily loaded at the time of the test.
The logs on the ticket above do not allow us to know which of the two "test_default_timeout" tests is failing, so disable both with self.skipTest().
Excerpt from ptest-runner python3:
test_default_timeout (test.test_multiprocessing_fork.test_manager.WithManagerTestBarrier.test_default_timeout)
SKIP: Test the barrier's default timeout 'skip flaky timeout test'
[YOCTO #15885]
--- ...kip-flaky-test_default_timeout-tests.patch | 49 +++++++++++++++++++ .../python/python3_3.13.11.bb | 1 + 2 files changed, 50 insertions(+) create mode 100644 meta/recipes-devtools/python/python3/0001-Skip-flaky-test_default_timeout-tests.patch
meta/recipes-devtools/python/python3/0001-Skip-flaky-test_default_timeout-tests.patch new file +49 -0
@@ -0,0 +1,49 @@ +From baf2dda48e51fcb17a716e52cc5c4e162a6bb7d3 Mon Sep 17 00:00:00 2001 +From: Antonin Godard <[email protected]> +Date: Mon, 19 Jan 2026 11:38:36 +0100 +Subject: [PATCH] Skip flaky test_default_timeout tests + +We have been observing issues with this test on the Autobuilder: +https://bugzilla.yoctoproject.org/show_bug.cgi?id=15885 + +The logs on the ticket above do not allow us to know which of the two +"test_default_timeout" tests is failing, so disable both with +self.skipTest(). + +Excerpt from `ptest-runner python3`: + + test_default_timeout (test.test_multiprocessing_fork.test_manager.WithManagerTestBarrier.test_default_timeout) + SKIP: Test the barrier's default timeout 'skip flaky timeout test' + +Upstream-Status: Inappropriate [OE specific, but might be related to https://github.com/python/cpython/issues/129266#issuecomment-2613058866] + +Signed-off-by: Antonin Godard <[email protected]> +--- + Lib/test/_test_multiprocessing.py | 1 + + Lib/test/lock_tests.py | 1 + + 2 files changed, 2 insertions(+) + +diff --git a/Lib/test/_test_multiprocessing.py b/Lib/test/_test_multiprocessing.py +index e8064e7..9ab1f9e 100644 +--- a/Lib/test/_test_multiprocessing.py ++++ b/Lib/test/_test_multiprocessing.py +@@ -2259,6 +2259,7 @@ class _TestBarrier(BaseTestCase): + """ + Test the barrier's default timeout + """ ++ self.skipTest('skip flaky timeout test') + barrier = self.Barrier(self.N, timeout=0.5) + results = self.DummyList() + self.run_threads(self._test_default_timeout_f, (barrier, results)) +diff --git a/Lib/test/lock_tests.py b/Lib/test/lock_tests.py +index 8c8f890..43e9b90 100644 +--- a/Lib/test/lock_tests.py ++++ b/Lib/test/lock_tests.py +@@ -1165,6 +1165,7 @@ class BarrierTests(BaseTestCase): + """ + Test the barrier's default timeout + """ ++ self.skipTest('skip flaky timeout test') + timeout = 0.100 + barrier = self.barriertype(2, timeout=timeout) + def f():
meta/recipes-devtools/python/python3_3.13.11.bb +1 -0
@@ -30,6 +30,7 @@ SRC_URI = "http://www.python.org/ftp/python/${PV}/Python-${PV}.tar.xz \ file://0001-test_active_children-skip-problematic-test.patch \ file://0001-test_readline-skip-limited-history-test.patch \ file://0001-Generate-data-for-OpenSSL-3.4-and-add-it-to-multissl.patch \ + file://0001-Skip-flaky-test_default_timeout-tests.patch \ " SRC_URI:append:class-native = " \ file://0001-Lib-sysconfig.py-use-prefix-value-from-build-configu.patch \
Quoted 11 lines · Yoann Congal
Please review this set of changes for whinlatter and have comments back by end of day Monday, March 9.
Passed a-full on autobuilder with warnings:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3334
The sub-build qemux86-64-ptest had a ptest failure
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3207
It is a known AB-INT bug: 15718 – AB-INT: gstreamer ptest never ending (Bitbake still alive)
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15718
This is not related to this series.
Quoted 8 lines
The following changes since commit
45cba1329d541fdc5857d6df2624b34c91133f7a:build-appliance-image: Update to whinlatter head revisions (2026-02-27 17:46:44 +0000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/whinlatter-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/whinlatter-nut
I plan to also add this patch to the branch:
[whinlatter][PATCH] create-pull-request: Keep commit hash to be pulled in cover email
https://lore.kernel.org/openembedded-core/[email protected]/T/#u
Quoted 76 lines
Adarsh Jagadish Kamini (1):
python3-pip: Backport fix CVE-2026-1703Ankur Tyagi (1):
wireless-regdb: upgrade 2025.10.07 -> 2026.02.04Antonin Godard (1):
python3: skip flakytest_default_timeouttestHugo SIMELIERE (2):
zlib: Fix CVE-2026-27171
harfbuzz: Fix CVE-2026-22693Peter Marko (3):
linux-yocto: apply cve-exclusions also to rt and tiny recipe variants
cve-exclusions: set status for 5 CVEs
ffmpeg: set status for CVE-2025-12343Shaik Moin (1):
gdk-pixbuf: Fix CVE-2025-6199Vijay Anusuri (1):
gnutls: Fix CVE-2025-14831Yoann Congal (2):
README: Add whinlatter subject-prefix to git-send-email suggestion
b4-config: add send-prefixes for whinlatter.b4-config | 1 + README.OE-Core.md | 2 +- .../zlib/zlib/CVE-2026-27171.patch | 63 +++ meta/recipes-core/zlib/zlib_1.3.1.bb | 1 + .../python/python3-pip/CVE-2026-1703.patch | 41 ++ .../python/python3-pip_25.2.bb | 4 +- ...kip-flaky-test_default_timeout-tests.patch | 49 ++ .../python/python3_3.13.11.bb | 1 + .../gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch | 36 ++ .../gdk-pixbuf/gdk-pixbuf_2.42.12.bb | 1 + .../harfbuzz/files/CVE-2026-22693.patch | 33 ++ .../harfbuzz/harfbuzz_11.4.5.bb | 4 +- meta/recipes-kernel/linux/cve-exclusion.inc | 16 + .../linux/linux-yocto-rt_6.12.bb | 1 + .../linux/linux-yocto-rt_6.16.bb | 1 + .../linux/linux-yocto-tiny_6.12.bb | 1 + .../linux/linux-yocto-tiny_6.16.bb | 1 + ....10.07.bb => wireless-regdb_2026.02.04.bb} | 2 +- meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.bb | 1 + .../gnutls/gnutls/CVE-2025-14831-1.patch | 119 +++++ .../gnutls/gnutls/CVE-2025-14831-10.patch | 424 +++++++++++++++ .../gnutls/gnutls/CVE-2025-14831-2.patch | 66 +++ .../gnutls/gnutls/CVE-2025-14831-3.patch | 30 ++ .../gnutls/gnutls/CVE-2025-14831-4.patch | 45 ++ .../gnutls/gnutls/CVE-2025-14831-5.patch | 205 +++++++ .../gnutls/gnutls/CVE-2025-14831-6.patch | 505 ++++++++++++++++++ .../gnutls/gnutls/CVE-2025-14831-7.patch | 124 +++++ .../gnutls/gnutls/CVE-2025-14831-8.patch | 155 ++++++ .../gnutls/gnutls/CVE-2025-14831-9.patch | 110 ++++ meta/recipes-support/gnutls/gnutls_3.8.10.bb | 10 + 30 files changed, 2048 insertions(+), 4 deletions(-) create mode 100644 meta/recipes-core/zlib/zlib/CVE-2026-27171.patch create mode 100644 meta/recipes-devtools/python/python3-pip/CVE-2026-1703.patch create mode 100644 meta/recipes-devtools/python/python3/0001-Skip-flaky-test_default_timeout-tests.patch create mode 100644 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch create mode 100644 meta/recipes-graphics/harfbuzz/files/CVE-2026-22693.patch rename meta/recipes-kernel/wireless-regdb/{wireless-regdb_2025.10.07.bb => wireless-regdb_2026.02.04.bb} (94%) create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-1.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-10.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-2.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-3.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-4.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-5.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-6.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-7.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-8.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-9.patch
Signature · 2 lines
Yoann Congal Smile ECS
Quoted 16 lines · Yoann Congal
Quoted 15 lines · Yoann Congal
Please review this set of changes for whinlatter and have comments back by end of day Monday, March 9.
Passed a-full on autobuilder with warnings:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3334
The sub-build qemux86-64-ptest had a ptest failure
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3207
It is a known AB-INT bug: 15718 – AB-INT: gstreamer ptest never ending (Bitbake still alive)
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15718
This is not related to this series.The following changes since commit
45cba1329d541fdc5857d6df2624b34c91133f7a:build-appliance-image: Update to whinlatter head revisions (2026-02-27 17:46:44 +0000)
Quoted 8 lines
Quoted 4 lines
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/whinlatter-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/whinlatter-nutI plan to also add this patch to the branch:
[whinlatter][PATCH] create-pull-request: Keep commit hash to be pulled in cover email
https://lore.kernel.org/openembedded-core/[email protected]/T/#u
And also:
[whinlatter][PATCH 1/2] avahi: Remove a reference to the rejected CVE-2021-36217 - Yoann Congal
https://lore.kernel.org/openembedded-core/[email protected]/
[whinlatter][PATCH 2/2] lz4: Remove a reference to the rejected CVE-2025-62813 - Yoann Congal
https://lore.kernel.org/openembedded-core/[email protected]/
Quoted 75 lines
Quoted 75 lines
Adarsh Jagadish Kamini (1):
python3-pip: Backport fix CVE-2026-1703Ankur Tyagi (1):
wireless-regdb: upgrade 2025.10.07 -> 2026.02.04Antonin Godard (1):
python3: skip flakytest_default_timeouttestHugo SIMELIERE (2):
zlib: Fix CVE-2026-27171
harfbuzz: Fix CVE-2026-22693Peter Marko (3):
linux-yocto: apply cve-exclusions also to rt and tiny recipe variants
cve-exclusions: set status for 5 CVEs
ffmpeg: set status for CVE-2025-12343Shaik Moin (1):
gdk-pixbuf: Fix CVE-2025-6199Vijay Anusuri (1):
gnutls: Fix CVE-2025-14831Yoann Congal (2):
README: Add whinlatter subject-prefix to git-send-email suggestion
b4-config: add send-prefixes for whinlatter.b4-config | 1 + README.OE-Core.md | 2 +- .../zlib/zlib/CVE-2026-27171.patch | 63 +++ meta/recipes-core/zlib/zlib_1.3.1.bb | 1 + .../python/python3-pip/CVE-2026-1703.patch | 41 ++ .../python/python3-pip_25.2.bb | 4 +- ...kip-flaky-test_default_timeout-tests.patch | 49 ++ .../python/python3_3.13.11.bb | 1 + .../gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch | 36 ++ .../gdk-pixbuf/gdk-pixbuf_2.42.12.bb | 1 + .../harfbuzz/files/CVE-2026-22693.patch | 33 ++ .../harfbuzz/harfbuzz_11.4.5.bb | 4 +- meta/recipes-kernel/linux/cve-exclusion.inc | 16 + .../linux/linux-yocto-rt_6.12.bb | 1 + .../linux/linux-yocto-rt_6.16.bb | 1 + .../linux/linux-yocto-tiny_6.12.bb | 1 + .../linux/linux-yocto-tiny_6.16.bb | 1 + ....10.07.bb => wireless-regdb_2026.02.04.bb} | 2 +- meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.bb | 1 + .../gnutls/gnutls/CVE-2025-14831-1.patch | 119 +++++ .../gnutls/gnutls/CVE-2025-14831-10.patch | 424 +++++++++++++++ .../gnutls/gnutls/CVE-2025-14831-2.patch | 66 +++ .../gnutls/gnutls/CVE-2025-14831-3.patch | 30 ++ .../gnutls/gnutls/CVE-2025-14831-4.patch | 45 ++ .../gnutls/gnutls/CVE-2025-14831-5.patch | 205 +++++++ .../gnutls/gnutls/CVE-2025-14831-6.patch | 505 ++++++++++++++++++ .../gnutls/gnutls/CVE-2025-14831-7.patch | 124 +++++ .../gnutls/gnutls/CVE-2025-14831-8.patch | 155 ++++++ .../gnutls/gnutls/CVE-2025-14831-9.patch | 110 ++++ meta/recipes-support/gnutls/gnutls_3.8.10.bb | 10 + 30 files changed, 2048 insertions(+), 4 deletions(-) create mode 100644 meta/recipes-core/zlib/zlib/CVE-2026-27171.patch create mode 100644 meta/recipes-devtools/python/python3-pip/CVE-2026-1703.patch create mode 100644 meta/recipes-devtools/python/python3/0001-Skip-flaky-test_default_timeout-tests.patch create mode 100644 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch create mode 100644 meta/recipes-graphics/harfbuzz/files/CVE-2026-22693.patch rename meta/recipes-kernel/wireless-regdb/{wireless-regdb_2025.10.07.bb => wireless-regdb_2026.02.04.bb} (94%) create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-1.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-10.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-2.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-3.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-4.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-5.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-6.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-7.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-8.patch create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2025-14831-9.patch
Signature · 2 lines
Yoann Congal Smile ECS