Patch review
cover Patch review
Please review this set of changes for kirkstone and have comments back by end of day Wednesday, March 18.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3429
This build was impacted by:
* 16185 – AB-INT: failed connections to git.yoctoproject.org https://bugzilla.yoctoproject.org/show_bug.cgi?id=16185
* https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/3403
* rebuilt successfully as https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/3404
* https://autobuilder.yoctoproject.org/valkyrie/#/builders/78/builds/3404
* rebuilt successfully as https://autobuilder.yoctoproject.org/valkyrie/#/builders/78/builds/3405
* A random network glitch on github:
* https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/3357
* rebuilt successfully as https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/3360
The following changes since commit 7b6c9faa301a6d058ca34e230586f6a81ffa3ffb:
build-appliance-image: Update to kirkstone head revision (2026-02-27 15:59:49 +0000)
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
for you to fetch changes up to ec995339f1f4143616f1b13814899acaf137b0b5:
createrepo-c: Fix createrepo-c-native build on GCC14 hosts (e.g. Fedora 41) (2026-03-15 23:59:54 +0100)
----------------------------------------------------------------
Aleksandar Nikolic (1):
scripts/install-buildtools: Update to 4.0.33
Hitendra Prajapati (1):
libpam: fix CVE-2024-10963
Ken Kurematsu (1):
libtheora: set CVE_PRODUCT
Martin Jansa (2):
libpam: re-add missing libgen include
lsb.py: strip ' from os-release file
Peter Marko (7):
alsa-lib: patch CVE-2026-25068
ffmpeg: patch CVE-2025-10256
inetutils: patch CVE-2026-28372
busybox: patch CVE-2025-60876
tiff: patch CVE-2025-61143
tiff: patch CVE-2025-61144
tiff: set status of CVE-2025-61145 as fixed by patch for CVE-2025-8961
Shaik Moin (1):
gdk-pixbuf: Fix CVE-2025-6199
Vijay Anusuri (1):
python3-pip: Fix CVE-2026-1703
Yoann Congal (3):
gtk+3: fix incompatible-pointer-types errors for native build on
Fedora 41
libcomps: Fix libcomps-native build on GCC14 hosts (e.g. Fedora 41)
createrepo-c: Fix createrepo-c-native build on GCC14 hosts (e.g.
Fedora 41)
meta/lib/oe/lsb.py | 2 +- .../inetutils/inetutils/CVE-2026-28372.patch | 86 +++++++ .../inetutils/inetutils_2.2.bb | 1 + .../busybox/busybox/CVE-2025-60876.patch | 38 +++ meta/recipes-core/busybox/busybox_1.35.0.bb | 1 + ...-proper-cast-for-PyMethodDef.ml_meth.patch | 41 ++++ .../createrepo-c/createrepo-c_0.19.0.bb | 1 + ...orrect-variable-for-category-and-env.patch | 48 ++++ .../libcomps/libcomps_0.1.18.bb | 1 + .../python/python3-pip/CVE-2026-1703.patch | 37 +++ .../python/python3-pip_22.0.3.bb | 1 + .../pam/libpam/CVE-2024-10963.patch | 229 ++++++++++++++++++ .../pam/libpam/CVE-2025-6020-01.patch | 4 +- meta/recipes-extended/pam/libpam_1.5.2.bb | 1 + .../gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch | 36 +++ .../gdk-pixbuf/gdk-pixbuf_2.42.10.bb | 1 + ...-type-when-calling-GtkWidget-methods.patch | 28 +++ ...ests-Add-GdkEvent-casts-in-testinput.patch | 48 ++++ meta/recipes-gnome/gtk+/gtk+3_3.24.34.bb | 2 + .../alsa/alsa-lib/CVE-2026-25068.patch | 34 +++ .../alsa/alsa-lib_1.2.6.1.bb | 1 + .../ffmpeg/ffmpeg/CVE-2025-10256.patch | 31 +++ .../recipes-multimedia/ffmpeg/ffmpeg_5.0.3.bb | 1 + .../libtheora/libtheora_1.1.1.bb | 2 + .../libtiff/tiff/CVE-2025-61143.patch | 44 ++++ .../libtiff/tiff/CVE-2025-61144.patch | 27 +++ .../libtiff/tiff/CVE-2025-8961.patch | 1 + meta/recipes-multimedia/libtiff/tiff_4.3.0.bb | 2 + scripts/install-buildtools | 4 +- 29 files changed, 748 insertions(+), 5 deletions(-) create mode 100644 meta/recipes-connectivity/inetutils/inetutils/CVE-2026-28372.patch create mode 100644 meta/recipes-core/busybox/busybox/CVE-2025-60876.patch create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0001-Use-proper-cast-for-PyMethodDef.ml_meth.patch create mode 100644 meta/recipes-devtools/libcomps/libcomps/0001-Fix-build-use-correct-variable-for-category-and-env.patch create mode 100644 meta/recipes-devtools/python/python3-pip/CVE-2026-1703.patch create mode 100644 meta/recipes-extended/pam/libpam/CVE-2024-10963.patch create mode 100644 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/CVE-2025-6199.patch create mode 100644 meta/recipes-gnome/gtk+/gtk+3/0001-Use-the-right-type-when-calling-GtkWidget-methods.patch create mode 100644 meta/recipes-gnome/gtk+/gtk+3/0002-tests-Add-GdkEvent-casts-in-testinput.patch create mode 100644 meta/recipes-multimedia/alsa/alsa-lib/CVE-2026-25068.patch create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2025-10256.patch create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2025-61143.patch create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2025-61144.patch
PATCH 1/17 libtheora: set CVE_PRODUCT
From: Ken Kurematsu <[email protected]>
In the NVD database, the product name of libtheora is theora. This was set to ensure that cve-check works correctly.
--- meta/recipes-multimedia/libtheora/libtheora_1.1.1.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-multimedia/libtheora/libtheora_1.1.1.bb +2 -0
@@ -17,6 +17,8 @@ SRC_URI[sha256sum] = "b6ae1ee2fa3d42ac489287d3ec34c5885730b1296f0801ae577a35193d UPSTREAM_CHECK_REGEX = "libtheora-(?P<pver>\d+(\.\d)+)\.(tar\.gz|tgz)" +CVE_PRODUCT = "theora" + inherit autotools pkgconfig EXTRA_OECONF = "--disable-examples"
PATCH 2/17 alsa-lib: patch CVE-2026-25068
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Pick patch mentioned in NVD report.
It also includes CVE ID in commit message.
Use older SNDERR funtion as new one is not yet available. This was copied from Debian patch.
--- .../alsa/alsa-lib/CVE-2026-25068.patch | 34 +++++++++++++++++++ .../alsa/alsa-lib_1.2.6.1.bb | 1 + 2 files changed, 35 insertions(+) create mode 100644 meta/recipes-multimedia/alsa/alsa-lib/CVE-2026-25068.patch
meta/recipes-multimedia/alsa/alsa-lib/CVE-2026-25068.patch new file +34 -0
@@ -0,0 +1,34 @@ +From 5f7fe33002d2d98d84f72e381ec2cccc0d5d3d40 Mon Sep 17 00:00:00 2001 +From: Jaroslav Kysela <[email protected]> +Date: Thu, 29 Jan 2026 16:51:09 +0100 +Subject: [PATCH] topology: decoder - add boundary check for channel mixer + count + +Malicious binary topology file may cause heap corruption. + +CVE: CVE-2026-25068 + +Signed-off-by: Jaroslav Kysela <[email protected]> + +Upstream-Status: Backport [https://github.com/alsa-project/alsa-lib/commit/5f7fe33002d2d98d84f72e381ec2cccc0d5d3d40] +Signed-off-by: Peter Marko <[email protected]> +--- + src/topology/ctl.c | 5 +++++ + 1 file changed, 5 insertions(+) + +diff --git a/src/topology/ctl.c b/src/topology/ctl.c +index a0c24518..322c461c 100644 +--- a/src/topology/ctl.c ++++ b/src/topology/ctl.c +@@ -1246,6 +1246,11 @@ int tplg_decode_control_mixer1(snd_tplg_t *tplg, + if (mc->num_channels > 0) { + map = tplg_calloc(heap, sizeof(*map)); + map->num_channels = mc->num_channels; ++ if (map->num_channels > SND_TPLG_MAX_CHAN || ++ map->num_channels > SND_SOC_TPLG_MAX_CHAN) { ++ SNDERR("mixer: unexpected channel count %d", map->num_channels); ++ return -EINVAL; ++ } + for (i = 0; i < map->num_channels; i++) { + map->channel[i].reg = mc->channel[i].reg; + map->channel[i].shift = mc->channel[i].shift;
meta/recipes-multimedia/alsa/alsa-lib_1.2.6.1.bb +1 -0
@@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=a916467b91076e631dd8edb7424769c7 \ " SRC_URI = "https://www.alsa-project.org/files/pub/lib/${BP}.tar.bz2" +SRC_URI += "file://CVE-2026-25068.patch" SRC_URI[sha256sum] = "ad582993d52cdb5fb159a0beab60a6ac57eab0cc1bdf85dc4db6d6197f02333f" inherit autotools pkgconfig
PATCH 3/17 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.10.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.10.bb +1 -0
@@ -21,6 +21,7 @@ SRC_URI = "${GNOME_MIRROR}/${BPN}/${MAJ_VER}/${BPN}-${PV}.tar.xz \ file://fatal-loader.patch \ file://0001-meson.build-allow-a-subset-of-tests-in-cross-compile.patch \ file://CVE-2025-7345.patch \ + file://CVE-2025-6199.patch \ " SRC_URI[sha256sum] = "ee9b6c75d13ba096907a2e3c6b27b61bcd17f5c7ebeab5a5b439d2f2e39fe44b"
PATCH 4/17 ffmpeg: patch CVE-2025-10256
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Pick patch metioned in NVD report.
--- .../ffmpeg/ffmpeg/CVE-2025-10256.patch | 31 +++++++++++++++++++ .../recipes-multimedia/ffmpeg/ffmpeg_5.0.3.bb | 1 + 2 files changed, 32 insertions(+) create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2025-10256.patch
meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2025-10256.patch new file +31 -0
@@ -0,0 +1,31 @@ +From a25462482c02c004d685a8fcf2fa63955aaa0931 Mon Sep 17 00:00:00 2001 +From: Jiasheng Jiang <[email protected]> +Date: Wed, 6 Aug 2025 16:39:47 +0000 +Subject: [PATCH] libavfilter/af_firequalizer: Add check for av_malloc_array() + +Add check for the return value of av_malloc_array() to avoid potential NULL pointer dereference. + +Fixes: d3be186ed1 ("avfilter/firequalizer: add dumpfile and dumpscale option") +Signed-off-by: Jiasheng Jiang <[email protected]> +Signed-off-by: Michael Niedermayer <[email protected]> + +CVE: CVE-2025-10256 +Upstream-Status: Backport [https://github.com/FFmpeg/FFmpeg/commit/a25462482c02c004d685a8fcf2fa63955aaa0931] +Signed-off-by: Peter Marko <[email protected]> +--- + libavfilter/af_firequalizer.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/libavfilter/af_firequalizer.c b/libavfilter/af_firequalizer.c +index 38663200eb..f14983b431 100644 +--- a/libavfilter/af_firequalizer.c ++++ b/libavfilter/af_firequalizer.c +@@ -793,6 +793,8 @@ static int config_input(AVFilterLink *inlink) + if (s->dumpfile) { + s->analysis_rdft = av_rdft_init(rdft_bits, DFT_R2C); + s->dump_buf = av_malloc_array(s->analysis_rdft_len, sizeof(*s->dump_buf)); ++ if (!s->dump_buf) ++ return AVERROR(ENOMEM); + } + + s->analysis_buf = av_malloc_array(s->analysis_rdft_len, sizeof(*s->analysis_buf));
meta/recipes-multimedia/ffmpeg/ffmpeg_5.0.3.bb +1 -0
@@ -53,6 +53,7 @@ SRC_URI = "https://www.ffmpeg.org/releases/${BP}.tar.xz \ file://CVE-2023-6602-CVE-2023-6604-CVE-2023-6605-0002.patch \ file://CVE-2023-6602-CVE-2023-6604-CVE-2023-6605-0003.patch \ file://CVE-2025-1594.patch \ + file://CVE-2025-10256.patch \ " SRC_URI[sha256sum] = "04c70c377de233a4b217c2fdf76b19aeb225a287daeb2348bccd978c47b1a1db"
PATCH 5/17 inetutils: patch CVE-2026-28372
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Pick patch according to [1] (equivalent to patch from [2]).
This CVE is needed if util-linux >= 2.40 is used which is not the case in Yocto kirkstone, however it's always possible that users update packages in their layers.
[1] https://security-tracker.debian.org/tracker/CVE-2026-28372
[2] https://nvd.nist.gov/vuln/detail/CVE-2026-28372
--- .../inetutils/inetutils/CVE-2026-28372.patch | 86 +++++++++++++++++++ .../inetutils/inetutils_2.2.bb | 1 + 2 files changed, 87 insertions(+) create mode 100644 meta/recipes-connectivity/inetutils/inetutils/CVE-2026-28372.patch
meta/recipes-connectivity/inetutils/inetutils/CVE-2026-28372.patch new file +86 -0
@@ -0,0 +1,86 @@ +From 4db2f19f4caac03c7f4da6363c140bd70df31386 Mon Sep 17 00:00:00 2001 +From: Erik Auerswald <[email protected]> +Date: Sun, 15 Feb 2026 15:38:50 +0100 +Subject: [PATCH] telnetd: don't allow systemd service credentials + +The login(1) implementation of util-linux added support for +systemd service credentials in release 2.40. This allows to +bypass authentication by specifying a directory name in the +environment variable CREDENTIALS_DIRECTORY. If this directory +contains a file named 'login.noauth' with the content of 'yes', +login(1) skips authentication. + +GNU Inetutils telnetd supports to set arbitrary environment +variables using the 'Environment' and 'New Environment' +Telnet options. This allows specifying a directory containing +'login.noauth'. A local user can create such a directory +and file, and, e.g., specify the user name 'root' to escalate +privileges. + +This problem was reported by Ron Ben Yizhak in +<https://lists.gnu.org/archive/html/bug-inetutils/2026-02/msg00000.html>. + +This commit clears CREDENTIALS_DIRECTORY from the environment +before executing login(1) to implement a simple fix that can +be backported easily. + +* NEWS.md: Mention fix. +* THANKS: Mention Ron Ben Yizhak. +* telnetd/pty.c: Clear CREDENTIALS_DIRECTORY from the environment +before executing 'login'. + +CVE: CVE-2026-28372 +Upstream-Status: Backport [https://cgit.git.savannah.gnu.org/cgit/inetutils.git/commit/?id=4db2f19f4caac03c7f4da6363c140bd70df31386] +Signed-off-by: Peter Marko <[email protected]> +--- + NEWS | 5 +++++ + THANKS | 1 + + telnetd/pty.c | 8 ++++++++ + 3 files changed, 14 insertions(+) + +diff --git a/NEWS b/NEWS +index 877ca53b..f5172a71 100644 +--- a/NEWS ++++ b/NEWS +@@ -1,5 +1,10 @@ + GNU inetutils NEWS -- history of user-visible changes. + ++** Prevent privilege escalation via telnetd abusing systemd service ++credentials support added to the login(1) implementation of util-linux ++in release 2.40. Reported by Ron Ben Yizhak in ++<https://lists.gnu.org/archive/html/bug-inetutils/2026-02/msg00000.html>. ++ + * Noteworthy changes in release 2.2 (2021-09-01) [stable] + + ** ftp +diff --git a/THANKS b/THANKS +index 8d1d3dbb..ef5f6063 100644 +--- a/THANKS ++++ b/THANKS +@@ -9,6 +9,7 @@ In particular: + NIIBE Yutaka (Security fixes & making talk finally work) + Nathan Neulinger (tftpd) + Thomas Bushnell (sockaddr sin_len field) ++ Ron Ben Yizhak (reported privilege escalation via telnetd) + + Please see version control logs and ChangeLog.? for full credits. + +diff --git a/telnetd/pty.c b/telnetd/pty.c +index c727e7be..f3518049 100644 +--- a/telnetd/pty.c ++++ b/telnetd/pty.c +@@ -132,6 +132,14 @@ start_login (char *host, int autologin, char *name) + if (!cmd) + fatal (net, "can't expand login command line"); + argcv_get (cmd, "", &argc, &argv); ++ ++ /* util-linux's "login" introduced an authentication bypass method ++ * via environment variable "CREDENTIALS_DIRECTORY" in version 2.40. ++ * Clear it from the environment before executing "login" to prevent ++ * abuse via Telnet. ++ */ ++ unsetenv ("CREDENTIALS_DIRECTORY"); ++ + execv (argv[0], argv); + syslog (LOG_ERR, "%s: %m\n", cmd); + fatalperror (net, cmd);
meta/recipes-connectivity/inetutils/inetutils_2.2.bb +1 -0
@@ -26,6 +26,7 @@ SRC_URI = "${GNU_MIRROR}/inetutils/inetutils-${PV}.tar.xz \ file://0002-CVE-2023-40303-Indent-changes-in-previous-commit.patch \ file://CVE-2026-24061-01.patch \ file://CVE-2026-24061-02.patch \ + file://CVE-2026-28372.patch \ " inherit autotools gettext update-alternatives texinfo
PATCH 6/17 busybox: patch CVE-2025-60876
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Although the patch was not merged yet, Debian already took it ([1]). Since busybox CVE handling is slow, follow Debian decision.
--- .../busybox/busybox/CVE-2025-60876.patch | 38 +++++++++++++++++++ meta/recipes-core/busybox/busybox_1.35.0.bb | 1 + 2 files changed, 39 insertions(+) create mode 100644 meta/recipes-core/busybox/busybox/CVE-2025-60876.patch
meta/recipes-core/busybox/busybox/CVE-2025-60876.patch new file +38 -0
@@ -0,0 +1,38 @@ +From 32c0f6f240fcb041ae7df44a9bbf958d627a8212 Mon Sep 17 00:00:00 2001 +From: Radoslav Kolev <[email protected]> +Date: Fri, 21 Nov 2025 11:21:18 +0200 +Subject: [PATCH] wget: don't allow control characters or spaces in the URL + +Fixes CVE-2025-60876 malicious URL can be used to inject +HTTP headers in the request. + +Signed-off-by: Radoslav Kolev <[email protected]> +Reviewed-by: Emmanuel Deloget <[email protected]> + +CVE: CVE-2025-60876 +Upstream-Status: Submitted [https://lists.busybox.net/pipermail/busybox/2025-November/091840.html] +Signed-off-by: Peter Marko <[email protected]> +--- + networking/wget.c | 9 +++++++++ + 1 file changed, 9 insertions(+) + +diff --git a/networking/wget.c b/networking/wget.c +index 9ec0e67..7602563 100644 +--- a/networking/wget.c ++++ b/networking/wget.c +@@ -536,6 +536,15 @@ static void parse_url(const char *src_url, struct host_info *h) + { + char *url, *p, *sp; + ++ /* Fix for CVE-2025-60876 - don't allow control characters or spaces in the URL */ ++ /* otherwise a malicious URL can be used to inject HTTP headers in the request */ ++ const unsigned char *u = (void *) src_url; ++ while (*u) { ++ if (*u <= ' ') ++ bb_simple_error_msg_and_die("Unencoded control character found in the URL!"); ++ u++; ++ } ++ + free(h->allocated); + h->allocated = url = xstrdup(src_url); +
meta/recipes-core/busybox/busybox_1.35.0.bb +1 -0
@@ -61,6 +61,7 @@ SRC_URI = "https://busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \ file://CVE-2023-39810.patch \ file://CVE-2025-46394-01.patch \ file://CVE-2025-46394-02.patch \ + file://CVE-2025-60876.patch \ " SRC_URI:append:libc-musl = " file://musl.cfg "
PATCH 7/17 tiff: patch CVE-2025-61143
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Pick patch from merge request mentioned in NVD report.
--- .../libtiff/tiff/CVE-2025-61143.patch | 44 +++++++++++++++++++ meta/recipes-multimedia/libtiff/tiff_4.3.0.bb | 1 + 2 files changed, 45 insertions(+) create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2025-61143.patch
meta/recipes-multimedia/libtiff/tiff/CVE-2025-61143.patch new file +44 -0
@@ -0,0 +1,44 @@ +From 4d28af5fe61b1760f10981f5072ff1e6fd44f210 Mon Sep 17 00:00:00 2001 +From: Lee Howard <[email protected]> +Date: Fri, 5 Sep 2025 21:44:49 +0000 +Subject: [PATCH] tiffcrop: avoid nullptr dereference + +Fixes #734 + +CVE: CVE-2025-61143 +Upstream-Status: Backport [https://gitlab.com/libtiff/libtiff/-/commit/4d28af5fe61b1760f10981f5072ff1e6fd44f210] +Signed-off-by: Peter Marko <[email protected]> +--- + tools/tiffcrop.c | 2 +- + tools/tiffdither.c | 5 +++++ + 2 files changed, 6 insertions(+), 1 deletion(-) + +diff --git a/tools/tiffcrop.c b/tools/tiffcrop.c +index ae414efc..1cbb49b6 100644 +--- a/tools/tiffcrop.c ++++ b/tools/tiffcrop.c +@@ -2561,7 +2561,7 @@ main(int argc, char* argv[]) + + if (dump.outfile != NULL) + { +- dump_info (dump.outfile, dump.format, "", "Completed run for %s", TIFFFileName(out)); ++ dump_info (dump.outfile, dump.format, "", "Completed run for %s", out ? TIFFFileName(out) : "(not opened)"); + fclose (dump.outfile); + } + } +diff --git a/tools/tiffdither.c b/tools/tiffdither.c +index 3c64fdc0..405527c7 100644 +--- a/tools/tiffdither.c ++++ b/tools/tiffdither.c +@@ -84,6 +84,11 @@ fsdither(TIFF* in, TIFF* out) + fprintf(stderr, "Out of memory.\n"); + goto skip_on_error; + } ++ if (imagewidth > TIFFScanlineSize(in)) ++ { ++ fprintf(stderr, "Image width exceeds scanline size.\n"); ++ goto skip_on_error; ++ } + + /* + * Get first line
meta/recipes-multimedia/libtiff/tiff_4.3.0.bb +1 -0
@@ -65,6 +65,7 @@ SRC_URI = "http://download.osgeo.org/libtiff/tiff-${PV}.tar.gz \ file://CVE-2025-9900.patch \ file://CVE-2025-8961.patch \ file://CVE-2025-9165.patch \ + file://CVE-2025-61143.patch \ " SRC_URI[sha256sum] = "0e46e5acb087ce7d1ac53cf4f56a09b221537fc86dfc5daaad1c2e89e1b37ac8"
PATCH 8/17 tiff: patch CVE-2025-61144
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Pick patch from merge request mentioned in NVD report.
--- .../libtiff/tiff/CVE-2025-61144.patch | 27 +++++++++++++++++++ meta/recipes-multimedia/libtiff/tiff_4.3.0.bb | 1 + 2 files changed, 28 insertions(+) create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2025-61144.patch
meta/recipes-multimedia/libtiff/tiff/CVE-2025-61144.patch new file +27 -0
@@ -0,0 +1,27 @@ +From 88cf9dbb48f6e172629795ecffae35d5052f68aa Mon Sep 17 00:00:00 2001 +From: Lee Howard <[email protected]> +Date: Fri, 5 Sep 2025 21:46:03 +0000 +Subject: [PATCH] tiffcrop: avoid buffer overflow + +Fixes #740 + +CVE: CVE-2025-61144 +Upstream-Status: Backport [https://gitlab.com/libtiff/libtiff/-/commit/88cf9dbb48f6e172629795ecffae35d5052f68aa] +Signed-off-by: Peter Marko <[email protected]> +--- + tools/tiffcrop.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/tools/tiffcrop.c b/tools/tiffcrop.c +index ae414efc..afa1cce5 100644 +--- a/tools/tiffcrop.c ++++ b/tools/tiffcrop.c +@@ -3913,7 +3913,7 @@ combineSeparateSamplesBytes (unsigned char *srcbuffs[], unsigned char *out, + { + if ((dumpfile != NULL) && (level == 2)) + { +- for (s = 0; s < spp; s++) ++ for (s = 0; (s < spp) && (s < MAX_SAMPLES); s++) + { + dump_info (dumpfile, format, "combineSeparateSamplesBytes","Input data, Sample %"PRIu16, s); + dump_buffer(dumpfile, format, 1, cols, row, srcbuffs[s] + (row * src_rowsize));
meta/recipes-multimedia/libtiff/tiff_4.3.0.bb +1 -0
@@ -66,6 +66,7 @@ SRC_URI = "http://download.osgeo.org/libtiff/tiff-${PV}.tar.gz \ file://CVE-2025-8961.patch \ file://CVE-2025-9165.patch \ file://CVE-2025-61143.patch \ + file://CVE-2025-61144.patch \ " SRC_URI[sha256sum] = "0e46e5acb087ce7d1ac53cf4f56a09b221537fc86dfc5daaad1c2e89e1b37ac8"
PATCH 9/17 tiff: set status of CVE-2025-61145 as fixed by patch for CVE-2025-8961
In reply to Yoann CongalFrom: Peter Marko <[email protected]>
Gitlab issues for these two CVEs mentioned in NVD inks lead to the same merge request.
--- meta/recipes-multimedia/libtiff/tiff/CVE-2025-8961.patch | 1 + 1 file changed, 1 insertion(+)
meta/recipes-multimedia/libtiff/tiff/CVE-2025-8961.patch +1 -0
@@ -6,6 +6,7 @@ Subject: [PATCH] tiffcrop: fix double-free and memory leak exposed by issue Upstream-Status: Backport [https://gitlab.com/libtiff/libtiff/-/commit/0ac97aa7a5bffddd88f7cdbe517264e9db3f5bd5] CVE: CVE-2025-8961 +CVE: CVE-2025-61145 Signed-off-by: Vijay Anusuri <[email protected]> --- tools/tiffcrop.c | 8 +++++++-
PATCH 10/17 gtk+3: fix incompatible-pointer-types errors for native build on Fedora 41
In reply to Yoann CongalFrom: Yoann Congal <[email protected]>
Backport 2 patchs to fix incompatible-pointer-types error when building
gtk+3-native on Fedora 41 host:
tests/testinput.c:197:79: error: passing argument 1 of ‘gdk_event_get_source_device’ from incompatible pointer type [-Wincompatible-pointer-types] gtk/gtklabel.c:4235:32: error: passing argument 1 of ‘gtk_widget_queue_resize’ from incompatible pointer type [-Wincompatible-pointer-types]
On autobuilder: fedora41-vk-1:~$ gcc --version
gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)
GCC 14 notoriously restricted how pointer types are converted:
https://gcc.gnu.org/gcc-14/porting_to.html#incompatible-pointer-types
--- ...-type-when-calling-GtkWidget-methods.patch | 28 +++++++++++ ...ests-Add-GdkEvent-casts-in-testinput.patch | 48 +++++++++++++++++++ meta/recipes-gnome/gtk+/gtk+3_3.24.34.bb | 2 + 3 files changed, 78 insertions(+) create mode 100644 meta/recipes-gnome/gtk+/gtk+3/0001-Use-the-right-type-when-calling-GtkWidget-methods.patch create mode 100644 meta/recipes-gnome/gtk+/gtk+3/0002-tests-Add-GdkEvent-casts-in-testinput.patch
meta/recipes-gnome/gtk+/gtk+3/0001-Use-the-right-type-when-calling-GtkWidget-methods.patch new file +28 -0
@@ -0,0 +1,28 @@ +From a3e82f20a1a1e7d8ffbc960a8bb4aa65b0d151ee Mon Sep 17 00:00:00 2001 +From: Yoann Congal <[email protected]> +Date: Tue, 6 Dec 2022 21:49:22 +0000 +Subject: [PATCH] Use the right type when calling GtkWidget methods + +From: Emmanuele Bassi <[email protected]> + +Let's avoid complaints from the compiler. + +Upstream-Status: Backport [https://gitlab.gnome.org/GNOME/gtk/-/commit/a3e82f20a1a1e7d8ffbc960a8bb4aa65b0d151ee] +Signed-off-by: Yoann Congal <[email protected]> +--- + gtk/gtklabel.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/gtk/gtklabel.c b/gtk/gtklabel.c +index 7933ab2af73..40a569004b6 100644 +--- a/gtk/gtklabel.c ++++ b/gtk/gtklabel.c +@@ -4232,7 +4232,7 @@ gtk_label_style_updated (GtkWidget *widget) + if (change == NULL || gtk_css_style_change_affects (change, GTK_CSS_AFFECTS_FONT)) + { + gtk_label_clear_layout (GTK_LABEL (widget)); +- gtk_widget_queue_resize (label); ++ gtk_widget_queue_resize (widget); + } + + if (change == NULL || gtk_css_style_change_affects (change, GTK_CSS_AFFECTS_TEXT_ATTRS) ||
meta/recipes-gnome/gtk+/gtk+3/0002-tests-Add-GdkEvent-casts-in-testinput.patch new file +48 -0
48 lines not on this page · raw message
meta/recipes-gnome/gtk+/gtk+3_3.24.34.bb +2 -0
@@ -7,6 +7,8 @@ SRC_URI = "${GNOME_MIRROR}/gtk+/${MAJ_VER}/gtk+-${PV}.tar.xz \ file://0003-Add-disable-opengl-configure-option.patch \ file://link_fribidi.patch \ file://CVE-2024-6655.patch \ + file://0001-Use-the-right-type-when-calling-GtkWidget-methods.patch \ + file://0002-tests-Add-GdkEvent-casts-in-testinput.patch \ " SRC_URI[sha256sum] = "dbc69f90ddc821b8d1441f00374dc1da4323a2eafa9078e61edbe5eeefa852ec"
PATCH 11/17 libpam: fix CVE-2024-10963
In reply to Yoann CongalFrom: Hitendra Prajapati <[email protected]>
Pick up "Mitigated by" patch from Debian security tracker. [0]: https://security-tracker.debian.org/tracker/CVE-2024-10963
patch[1] which fixes this vulnerability as mentioned in Debian report.
[1] https://github.com/linux-pam/linux-pam/commit/940747f88c16e029b69a74e80a2e94f65cb3e628
[YC: Debian security tracker: "The vulnerable code was introduced in 1.5.3" but the vulnerable code was backported in commit 399d4986a7 (libpam: fix CVE-2022-28321, 2022-10-28)]
--- .../pam/libpam/CVE-2024-10963.patch | 229 ++++++++++++++++++ meta/recipes-extended/pam/libpam_1.5.2.bb | 1 + 2 files changed, 230 insertions(+) create mode 100644 meta/recipes-extended/pam/libpam/CVE-2024-10963.patch
meta/recipes-extended/pam/libpam/CVE-2024-10963.patch new file +229 -0
@@ -0,0 +1,229 @@ +From f9ccee5c4c6cb0d4197b08ebeb36c1dceffe82e8 Mon Sep 17 00:00:00 2001 +From: Thorsten Kukuk <[email protected]> +Date: Thu, 14 Nov 2024 10:27:28 +0100 +Subject: [PATCH] pam_access: rework resolving of tokens as hostname + +* modules/pam_access/pam_access.c: separate resolving of IP addresses + from hostnames. Don't resolve TTYs or display variables as hostname + (#834). + Add "nodns" option to disallow resolving of tokens as hostname. +* modules/pam_access/pam_access.8.xml: document nodns option +* modules/pam_access/access.conf.5.xml: document that hostnames should + be written as FQHN. + +CVE: CVE-2024-10963 +Upstream-Status: Backport [https://github.com/linux-pam/linux-pam/commit/940747f88c16e029b69a74e80a2e94f65cb3e628] +Signed-off-by: Hitendra Prajapati <[email protected]> +--- + modules/pam_access/access.conf.5.xml | 4 ++ + modules/pam_access/pam_access.8.xml | 46 ++++++++++++------ + modules/pam_access/pam_access.c | 72 +++++++++++++++++++++++++++- + 3 files changed, 105 insertions(+), 17 deletions(-) + +diff --git a/modules/pam_access/access.conf.5.xml b/modules/pam_access/access.conf.5.xml +index 8fdbc31..dc505a6 100644 +--- a/modules/pam_access/access.conf.5.xml ++++ b/modules/pam_access/access.conf.5.xml +@@ -226,6 +226,10 @@ + item and the line will be most probably ignored. For this reason, it is not + recommended to put spaces around the ':' characters. + </para> ++ <para> ++ Hostnames should be written as Fully-Qualified Host Name (FQHN) to avoid ++ confusion with device names or PAM service names. ++ </para> + </refsect1> + + <refsect1 id="access.conf-see_also"> +diff --git a/modules/pam_access/pam_access.8.xml b/modules/pam_access/pam_access.8.xml +index 9a6556c..eab9d9f 100644 +--- a/modules/pam_access/pam_access.8.xml ++++ b/modules/pam_access/pam_access.8.xml +@@ -25,11 +25,14 @@ + <arg choice="opt"> + debug + </arg> ++ <arg choice="opt" rep="norepeat"> ++ noaudit ++ </arg> + <arg choice="opt"> + nodefgroup + </arg> + <arg choice="opt"> +- noaudit ++ nodns + </arg> + <arg choice="opt"> + accessfile=<replaceable>file</replaceable> +@@ -112,6 +115,33 @@ + </listitem> + </varlistentry> + ++ <varlistentry> ++ <term> ++ nodefgroup ++ </term> ++ <listitem> ++ <para> ++ User tokens which are not enclosed in parentheses will not be ++ matched against the group database. The backwards compatible default is ++ to try the group database match even for tokens not enclosed ++ in parentheses. ++ </para> ++ </listitem> ++ </varlistentry> ++ ++ <varlistentry> ++ <term> ++ nodns ++ </term> ++ <listitem> ++ <para> ++ Do not try to resolve tokens as hostnames, only IPv4 and IPv6 ++ addresses will be resolved. Which means to allow login from a ++ remote host, the IP addresses need to be specified in <filename>access.conf</filename>. ++ </para> ++ </listitem> ++ </varlistentry> ++ + <varlistentry> + <term> + <option>fieldsep=<replaceable>separators</replaceable></option> +@@ -153,20 +183,6 @@ + </listitem> + </varlistentry> + +- <varlistentry> +- <term> +- <option>nodefgroup</option> +- </term> +- <listitem> +- <para> +- User tokens which are not enclosed in parentheses will not be +- matched against the group database. The backwards compatible default is +- to try the group database match even for tokens not enclosed +- in parentheses. +- </para> +- </listitem> +- </varlistentry> +- + </variablelist> + </refsect1> + +diff --git a/modules/pam_access/pam_access.c b/modules/pam_access/pam_access.c +index bca424f..00a0a77 100644 +--- a/modules/pam_access/pam_access.c ++++ b/modules/pam_access/pam_access.c +@@ -92,6 +92,7 @@ struct login_info { + int debug; /* Print debugging messages. */ + int only_new_group_syntax; /* Only allow group entries of the form "(xyz)" */ + int noaudit; /* Do not audit denials */ ++ int nodns; /* Do not try to resolve tokens as hostnames */ + const char *fs; /* field separator */ + const char *sep; /* list-element separator */ + int from_remote_host; /* If PAM_RHOST was used for from */ +@@ -143,6 +144,8 @@ parse_args(pam_handle_t *pamh, struct login_info *loginfo, + loginfo->only_new_group_syntax = YES; + } else if (strcmp (argv[i], "noaudit") == 0) { + loginfo->noaudit = YES; ++ } else if (strcmp (argv[i], "nodns") == 0) { ++ loginfo->nodns = YES; + } else { + pam_syslog(pamh, LOG_ERR, "unrecognized option [%s]", argv[i]); + } +@@ -637,7 +640,7 @@ remote_match (pam_handle_t *pamh, char *tok, struct login_info *item) + if ((str_len = strlen(string)) > tok_len + && strcasecmp(tok, string + str_len - tok_len) == 0) + return YES; +- } else if (tok[tok_len - 1] == '.') { /* internet network numbers (end with ".") */ ++ } else if (tok[tok_len - 1] == '.') { /* internet network numbers/subnet (end with ".") */ + struct addrinfo hint; + + memset (&hint, '\0', sizeof (hint)); +@@ -712,6 +715,39 @@ string_match (pam_handle_t *pamh, const char *tok, const char *string, + } + + ++static int ++is_device (pam_handle_t *pamh, const char *tok) ++{ ++ struct stat st; ++ const char *dev = "/dev/"; ++ char *devname; ++ ++ devname = malloc (strlen(dev) + strlen (tok) + 1); ++ if (devname == NULL) { ++ pam_syslog(pamh, LOG_ERR, "Cannot allocate memory for device name: %m"); ++ /* ++ * We should return an error and abort, but pam_access has no good ++ * error handling. ++ */ ++ return NO; ++ } ++ ++ char *cp = stpcpy (devname, dev); ++ strcpy (cp, tok); ++ ++ if (lstat(devname, &st) != 0) ++ { ++ free (devname); ++ return NO; ++ } ++ free (devname); ++ ++ if (S_ISCHR(st.st_mode)) ++ return YES; ++ ++ return NO; ++} ++ + /* network_netmask_match - match a string against one token + * where string is a hostname or ip (v4,v6) address and tok + * represents either a hostname, a single ip (v4,v6) address +@@ -773,10 +809,42 @@ network_netmask_match (pam_handle_t *pamh, + return NO; + } + } ++ else if (isipaddr(tok, NULL, NULL) == YES) ++ { ++ if (getaddrinfo (tok, NULL, NULL, &ai) != 0) ++ { ++ if (item->debug) ++ pam_syslog(pamh, LOG_DEBUG, "cannot resolve IP address \"%s\"", tok); ++ ++ return NO; ++ } ++ netmask_ptr = NULL; ++ } ++ else if (item->nodns) ++ { ++ /* Only hostnames are left, which we would need to resolve via DNS */ ++ return NO; ++ } + else + { ++ /* Bail out on X11 Display entries and ttys. */ ++ if (tok[0] == ':') ++ { ++ if (item->debug) ++ pam_syslog (pamh, LOG_DEBUG, ++ "network_netmask_match: tok=%s is X11 display", tok); ++ return NO; ++ } ++ if (is_device (pamh, tok)) ++ { ++ if (item->debug) ++ pam_syslog (pamh, LOG_DEBUG, ++ "network_netmask_match: tok=%s is a TTY", tok); ++ return NO; ++ } ++ + /* +- * It is either an IP address or a hostname. ++ * It is most likely a hostname. + * Let getaddrinfo sort everything out + */ + if (getaddrinfo (tok, NULL, NULL, &ai) != 0) +-- +2.50.1 +
meta/recipes-extended/pam/libpam_1.5.2.bb +1 -0
@@ -34,6 +34,7 @@ SRC_URI = "https://github.com/linux-pam/linux-pam/releases/download/v${PV}/Linux file://CVE-2025-6020-01.patch \ file://CVE-2025-6020-02.patch \ file://CVE-2025-6020-03.patch \ + file://CVE-2024-10963.patch \ " SRC_URI[sha256sum] = "e4ec7131a91da44512574268f493c6d8ca105c87091691b8e9b56ca685d4f94d"
PATCH 12/17 libpam: re-add missing libgen include
In reply to Yoann CongalFrom: Martin Jansa <[email protected]>
It was added by original commit for CVE-2025-6020-01.patch
https://github.com/linux-pam/linux-pam/commit/475bd60c552b98c7eddb3270b0b4196847c0072e#diff-05f443e6acbe32a148a45648148739bf6f02f13acc5c20c6037bf933223d4d77
but removed here in the rebase, causing:
../../../Linux-PAM-1.5.3/modules/pam_namespace/pam_namespace.c:326:11: error: call to undeclared function 'dirname'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
326 | parent = dirname(buf);
| ^../../../Linux-PAM-1.5.3/modules/pam_namespace/pam_namespace.c:326:9: error: incompatible integer to pointer conversion assigning to 'char*' from 'int' [-Wint-conversion]
326 | parent = dirname(buf);
| ^ ~~~~~~~~~~~~Backport 6d88a28ac7b6ff61808eb46e5c85dabd17c77f2e from scarthgap. It's reproducible with clang-18 from kirkstone-clang18 branch of meta-clang.
--- meta/recipes-extended/pam/libpam/CVE-2025-6020-01.patch | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
meta/recipes-extended/pam/libpam/CVE-2025-6020-01.patch +2 -2
@@ -1528,7 +1528,7 @@ diff --git a/modules/pam_namespace/pam_namespace.h b/modules/pam_namespace/pam_n index b51f284..abd570d 100644 --- a/modules/pam_namespace/pam_namespace.h +++ b/modules/pam_namespace/pam_namespace.h -@@ -44,21 +44,16 @@ +@@ -44,21 +44,17 @@ #include <stdlib.h> #include <errno.h> #include <syslog.h>
@@ -1542,7 +1542,7 @@ index b51f284..abd570d 100644 -#include <sys/resource.h> #include <sys/mount.h> #include <sys/wait.h> --#include <libgen.h> + #include <libgen.h> #include <fcntl.h> #include <sched.h> #include <glob.h>
PATCH 13/17 lsb.py: strip ' from os-release file
In reply to Yoann CongalFrom: Martin Jansa <[email protected]>
In gentoo the file looks like this:
NAME='Gentoo'
ID='gentoo'
PRETTY_NAME='Gentoo Linux'
VERSION='2.18'
VERSION_ID='2.18'
HOME_URL='https://www.gentoo.org/'
SUPPORT_URL='https://www.gentoo.org/support/'
BUG_REPORT_URL='https://bugs.gentoo.org/'
ANSI_COLOR='1;32'
' were added with:
https://github.com/gentoo/gentoo/commit/2f590e35c9d3d13d5673163527120b2de97fdc80
before that the os-release file looked like this:
NAME=Gentoo
ID=gentoo
PRETTY_NAME="Gentoo Linux"
ANSI_COLOR="1;32"
HOME_URL="https://www.gentoo.org/"
SUPPORT_URL="https://www.gentoo.org/support/"
BUG_REPORT_URL="https://bugs.gentoo.org/"
VERSION_ID="2.18"
The ' is stripped from the ID later in distro_identifier with:
# Filter out any non-alphanumerics and convert to lowercase distro_id = re.sub(r'\W', '', distro_id).lower()
but not from version which results in a weird NATIVELSBSTRING like:
NATIVELSBSTRING = "gentoo-'2.18'"
And similarly the directory name in sstate-cache:
oe-core $ ls -d sstate-cache/gentoo-*
"sstate-cache/gentoo-'2.18'" sstate-cache/gentoo-2.18
--- meta/lib/oe/lsb.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/lib/oe/lsb.py +1 -1
@@ -14,7 +14,7 @@ def get_os_release(): key, val = line.rstrip().split('=', 1) except ValueError: continue - data[key.strip()] = val.strip('"') + data[key.strip()] = val.strip('"\'') return data def release_dict_osr():
PATCH 14/17 python3-pip: Fix CVE-2026-1703
In reply to Yoann CongalFrom: Vijay Anusuri <[email protected]>
Pick patch according to [1]
[1] https://security-tracker.debian.org/tracker/CVE-2026-1703
[2] https://nvd.nist.gov/vuln/detail/CVE-2026-1703
[3] https://github.com/pypa/pip/pull/13777
--- .../python/python3-pip/CVE-2026-1703.patch | 37 +++++++++++++++++++ .../python/python3-pip_22.0.3.bb | 1 + 2 files changed, 38 insertions(+) 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 +37 -0
@@ -0,0 +1,37 @@ +From 4c651b70d60ed91b13663bcda9b3ed41748d0124 Mon Sep 17 00:00:00 2001 +From: Seth Michael Larson <[email protected]> +Date: Fri, 30 Jan 2026 09:49:11 -0600 +Subject: [PATCH] Use os.path.commonpath() instead of commonprefix() + +Upstream-Status: Backport [https://github.com/pypa/pip/commit/4c651b70d60ed91b13663bcda9b3ed41748d0124] +CVE: CVE-2026-1703 +Signed-off-by: Vijay Anusuri <[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 0000000..edb1b32 +--- /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 5f63f97..3cebbf7 100644 +--- a/src/pip/_internal/utils/unpacking.py ++++ b/src/pip/_internal/utils/unpacking.py +@@ -81,7 +81,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.25.1 +
meta/recipes-devtools/python/python3-pip_22.0.3.bb +1 -0
@@ -38,6 +38,7 @@ SRC_URI += "file://0001-change-shebang-to-python3.patch \ file://no_shebang_mangling.patch \ file://reproducible.patch \ file://CVE-2023-5752.patch \ + file://CVE-2026-1703.patch \ " SRC_URI[sha256sum] = "f29d589df8c8ab99c060e68ad294c4a9ed896624f6368c5349d70aa581b333d0"
PATCH 15/17 scripts/install-buildtools: Update to 4.0.33
In reply to Yoann CongalFrom: Aleksandar Nikolic <[email protected]>
Update to the 4.0.33 release of the 4.0 series for buildtools
--- scripts/install-buildtools | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
scripts/install-buildtools +2 -2
@@ -57,8 +57,8 @@ logger = scriptutils.logger_create(PROGNAME, stream=sys.stdout) DEFAULT_INSTALL_DIR = os.path.join(os.path.split(scripts_path)[0],'buildtools') DEFAULT_BASE_URL = 'https://downloads.yoctoproject.org/releases/yocto' -DEFAULT_RELEASE = 'yocto-4.0.32' -DEFAULT_INSTALLER_VERSION = '4.0.32' +DEFAULT_RELEASE = 'yocto-4.0.33' +DEFAULT_INSTALLER_VERSION = '4.0.33' DEFAULT_BUILDDATE = '202110XX' # Python version sanity check
PATCH 16/17 libcomps: Fix libcomps-native build on GCC14 hosts (e.g. Fedora 41)
In reply to Yoann CongalFrom: Yoann Congal <[email protected]>
This version of libcomps does wrong pointer assignment, and on GCC14
hosts (e.g. Fedora 41), this fails to build with:
| build/tmp-glibc/work/x86_64-linux/libcomps-native/0.1.18-r0/git/libcomps/tests/check_parse.c:588:11: error: assignment to ‘COMPS_DocGroup *’ from incompatible pointer type ‘COMPS_DocCategory *’ [-Wincompatible-pointer-types]
| 588 | g = (COMPS_DocCategory*)it->comps_obj;
Backport a patch making the assignment correct.
--- ...orrect-variable-for-category-and-env.patch | 48 +++++++++++++++++++ .../libcomps/libcomps_0.1.18.bb | 1 + 2 files changed, 49 insertions(+) create mode 100644 meta/recipes-devtools/libcomps/libcomps/0001-Fix-build-use-correct-variable-for-category-and-env.patch
meta/recipes-devtools/libcomps/libcomps/0001-Fix-build-use-correct-variable-for-category-and-env.patch new file +48 -0
@@ -0,0 +1,48 @@ +From adcf4aaca08ea712af4b4e886931fd8ed59c7bf7 Mon Sep 17 00:00:00 2001 +From: Aleš Matěj <[email protected]> +Date: Tue, 2 Jan 2024 08:32:55 +0100 +Subject: [PATCH] Fix build: use correct variable for category and env +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +Fixes: +- error: assignment to ‘COMPS_DocGroup *’ from incompatible pointer type ‘COMPS_DocCategory *’ +- error: assignment to ‘COMPS_DocGroup *’ from incompatible pointer type ‘COMPS_DocEnv *’ + +For: https://fedoraproject.org/wiki/Changes/PortingToModernC +(https://fedoraproject.org/wiki/Toolchain/PortingToModernC) +(https://gitlab.com/fweimer-rh/fedora-modernc-logs/-/blob/main/logs/l/libcomps.log) + +Upstream-Status: Backport [https://github.com/rpm-software-management/libcomps/commit/a71bce7e62990550a57688e51b14eb82d6de196b] +Signed-off-by: Yoann Congal <[email protected]> +--- + libcomps/tests/check_parse.c | 8 ++++---- + 1 file changed, 4 insertions(+), 4 deletions(-) + +diff --git a/libcomps/tests/check_parse.c b/libcomps/tests/check_parse.c +index e5935e1..689cb98 100644 +--- a/libcomps/tests/check_parse.c ++++ b/libcomps/tests/check_parse.c +@@ -585,8 +585,8 @@ START_TEST(test_arch) + list = comps_doc_categories(doc2); + ck_assert(list->len == 2); + for (it = list->first, x=0; it != NULL; it = it->next, x++) { +- g = (COMPS_DocCategory*)it->comps_obj; +- str = (COMPS_Str*)comps_doccategory_get_id(g); ++ c = (COMPS_DocCategory*)it->comps_obj; ++ str = (COMPS_Str*)comps_doccategory_get_id(c); + ck_assert_msg(strcmp(str->val, cats[0][x]) == 0, "%s != %s", + str->val, cats[0][x]); + COMPS_OBJECT_DESTROY(str); +@@ -605,8 +605,8 @@ START_TEST(test_arch) + list = comps_doc_environments(doc2); + ck_assert(list->len == 2); + for (it = list->first, x=0; it != NULL; it = it->next, x++) { +- g = (COMPS_DocEnv*)it->comps_obj; +- str = (COMPS_Str*)comps_docenv_get_id(g); ++ e = (COMPS_DocEnv*)it->comps_obj; ++ str = (COMPS_Str*)comps_docenv_get_id(e); + ck_assert_msg(strcmp(str->val, envs[0][x]) == 0, "%s != %s", + str->val, envs[0][x]); + COMPS_OBJECT_DESTROY(str);
meta/recipes-devtools/libcomps/libcomps_0.1.18.bb +1 -0
@@ -6,6 +6,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263" SRC_URI = "git://github.com/rpm-software-management/libcomps.git;branch=master;protocol=https \ file://0002-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch \ + file://0001-Fix-build-use-correct-variable-for-category-and-env.patch \ " SRCREV = "dee4ae37f7818709802de28c4d16fa823bd83ae2"
PATCH 17/17 createrepo-c: Fix createrepo-c-native build on GCC14 hosts (e.g. Fedora 41)
In reply to Yoann CongalFrom: Yoann Congal <[email protected]>
This version of createrepo-c does a wrong pointer assignment, and on GCC14[0]
hosts (e.g. Fedora 41), this fails to build with:
FAILED: src/python/CMakeFiles/_createrepo_c.dir/createrepo_cmodule.c.o
build/tmp-glibc/hosttools/gcc [...] python/createrepo_cmodule.c
python/createrepo_cmodule.c:82:41: error: initialization of ‘PyObject * (*)(PyObject *, PyObject *)’ {aka ‘struct _object * (*)(struct _object *, struct _object *)’} from incompatible pointer type ‘PyObject * (*)(PyObject *, PyObject *, PyObject *)’ {aka ‘struct _object * (*)(struct _object *, struct _object *, struct _object *)’} [-Wincompatible-pointer-types]
82 | {"xml_parse_main_metadata_together",(PyCFunctionWithKeywords)py_xml_parse_main_metadata_together,
| ^
src/python/createrepo_cmodule.c:82:41: note: (near initialization for ‘createrepo_c_methods[15].ml_meth’)
Add a patch to fix the pointer assignment. The patched code has since been removed by upstream.
[0]: https://gcc.gnu.org/gcc-14/porting_to.html#incompatible-pointer-types
--- ...-proper-cast-for-PyMethodDef.ml_meth.patch | 41 +++++++++++++++++++ .../createrepo-c/createrepo-c_0.19.0.bb | 1 + 2 files changed, 42 insertions(+) create mode 100644 meta/recipes-devtools/createrepo-c/createrepo-c/0001-Use-proper-cast-for-PyMethodDef.ml_meth.patch
meta/recipes-devtools/createrepo-c/createrepo-c/0001-Use-proper-cast-for-PyMethodDef.ml_meth.patch new file +41 -0
@@ -0,0 +1,41 @@ +From d2dd32bcdcc717a0da48d5e983c4396ccc79fc9c Mon Sep 17 00:00:00 2001 +From: Yoann Congal <[email protected]> +Date: Sun, 15 Mar 2026 23:25:16 +0100 +Subject: [PATCH] Use proper cast for PyMethodDef.ml_meth +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +PyMethodDef.ml_meth is of PyCFunction type. Using a +PyCFunctionWithKeywords cast for its initializer trigger build failure +with GCC >=14 [0]: +| FAILED: src/python/CMakeFiles/_createrepo_c.dir/createrepo_cmodule.c.o +| build/tmp-glibc/hosttools/gcc [...] python/createrepo_cmodule.c +| python/createrepo_cmodule.c:82:41: error: initialization of ‘PyObject * (*)(PyObject *, PyObject *)’ {aka ‘struct _object * (*)(struct _object *, struct _object *)’} from incompatible pointer type ‘PyObject * (*)(PyObject *, PyObject *, PyObject *)’ {aka ‘struct _object * (*)(struct _object *, struct _object *, struct _object *)’} [-Wincompatible-pointer-types] +| 82 | {"xml_parse_main_metadata_together",(PyCFunctionWithKeywords)py_xml_parse_main_metadata_together, +| | ^ +| src/python/createrepo_cmodule.c:82:41: note: (near initialization for ‘createrepo_c_methods[15].ml_meth’) + +Fix this by using the proper (PyCFunction) cast. + +[0]: https://gcc.gnu.org/gcc-14/porting_to.html#incompatible-pointer-types + +Upstream-Status: Inappropriate [Upstream removed the patched code in 7092ab2 (Remove python bindings for xml_parse_main_metadata_together, 2022-03-17)] +Signed-off-by: Yoann Congal <[email protected]> +--- + src/python/createrepo_cmodule.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/src/python/createrepo_cmodule.c b/src/python/createrepo_cmodule.c +index c0b9200..94a206d 100644 +--- a/src/python/createrepo_cmodule.c ++++ b/src/python/createrepo_cmodule.c +@@ -79,7 +79,7 @@ static struct PyMethodDef createrepo_c_methods[] = { + METH_VARARGS, xml_parse_repomd__doc__}, + {"xml_parse_updateinfo", (PyCFunction)py_xml_parse_updateinfo, + METH_VARARGS, xml_parse_updateinfo__doc__}, +- {"xml_parse_main_metadata_together",(PyCFunctionWithKeywords)py_xml_parse_main_metadata_together, ++ {"xml_parse_main_metadata_together",(PyCFunction)py_xml_parse_main_metadata_together, + METH_VARARGS | METH_KEYWORDS, xml_parse_main_metadata_together__doc__}, + {"checksum_name_str", (PyCFunction)py_checksum_name_str, + METH_VARARGS, checksum_name_str__doc__},
meta/recipes-devtools/createrepo-c/createrepo-c_0.19.0.bb +1 -0
@@ -6,6 +6,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263" SRC_URI = "git://github.com/rpm-software-management/createrepo_c;branch=master;protocol=https \ file://0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch \ + file://0001-Use-proper-cast-for-PyMethodDef.ml_meth.patch \ " SRCREV = "a531ee881a8f1d9273b4383fb9fa604c56fff138"