Patch review
cover Patch review
Please review this set of changes for scarthgap and have comments back by end of day Tuesday, October 6.
Note: this series includes an expat version upgrade. This is an exception to the usual stable policy, accepted because it should not break any existing code and help a lot with CVEs.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/29/builds/4868
* qemux86-tc failed with
Bug 14259 - AB-INT: NFS mounting issue on qemu oe-selftest glibc.GlibcSelfTestSystemEmulated.test_glibc that I reopened.
Retried in https://autobuilder.yoctoproject.org/valkyrie/?#/builders/28/builds/4746
* oe-selftest-fedora failed with
Bug 16206 - [scarthgap] AB-INT: runtime_test.SystemTap.test_crosstap_* failures Retried in https://autobuilder.yoctoproject.org/valkyrie/?#/builders/48/builds/4801
The following changes since commit 07ca97baad7b182849ee50f0bd629b68dc9f53b3:
time64: enable 64-bit time/file-offset flags for 32-bit nativesdk (2026-09-24 08:54:34 +0200)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/scarthgap-review
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/scarthgap-review
for you to fetch changes up to 827730f97b522c4ab31dd2b7b5a33a4933c94750:
python3-pyasn1: fix CVE-2026-59885 (2026-10-02 17:46:50 +0200)
----------------------------------------------------------------
Deepesh Varatharajan (1):
glibc: Fix CVE-2026-6238
Devansh Patel (1):
vim: Fix CVE-2026-28417 regressions
Jakub Szczudlo (Nokia) (1):
expat: upgrade 2.6.4 -> 2.8.3, exception security update
Richard Purdie (2):
sstate: Update mtime/atime for sig/siginfo files in
sstate_checkhashes()
sstate: Update unpack touch code to be consistent
Tim Orling (1):
at-spi2-core: RDEPENDS on gsettings-desktop-schemas
Yogita Urade (2):
python3-pyasn1: fix CVE-2026-30922
python3-pyasn1: fix CVE-2026-59885
meta/classes-global/sstate.bbclass | 16 +- ...ests-Cover-indirect-entity-recursion.patch | 103 -- .../expat/expat/CVE-2024-8176-01.patch | 1477 ----------------- .../expat/expat/CVE-2024-8176-02.patch | 248 --- .../expat/expat/CVE-2024-8176-03.patch | 35 - .../expat/expat/CVE-2024-8176-04.patch | 115 -- .../expat/expat/CVE-2024-8176-05.patch | 78 - .../expat/expat/CVE-2025-59375-00.patch | 52 - .../expat/expat/CVE-2025-59375-01.patch | 48 - .../expat/expat/CVE-2025-59375-02.patch | 109 -- .../expat/expat/CVE-2025-59375-03.patch | 127 -- .../expat/expat/CVE-2025-59375-04.patch | 62 - .../expat/expat/CVE-2025-59375-05.patch | 64 - .../expat/expat/CVE-2025-59375-06.patch | 68 - .../expat/expat/CVE-2025-59375-07.patch | 52 - .../expat/expat/CVE-2025-59375-08.patch | 577 ------- .../expat/expat/CVE-2025-59375-09.patch | 43 - .../expat/expat/CVE-2025-59375-10.patch | 54 - .../expat/expat/CVE-2025-59375-11.patch | 66 - .../expat/expat/CVE-2025-59375-12.patch | 58 - .../expat/expat/CVE-2025-59375-13.patch | 309 ---- .../expat/expat/CVE-2025-59375-14.patch | 122 -- .../expat/expat/CVE-2025-59375-15.patch | 70 - .../expat/expat/CVE-2025-59375-16.patch | 146 -- .../expat/expat/CVE-2025-59375-17.patch | 28 - .../expat/expat/CVE-2025-59375-18.patch | 74 - .../expat/expat/CVE-2025-59375-19.patch | 103 -- .../expat/expat/CVE-2025-59375-20.patch | 285 ---- .../expat/expat/CVE-2025-59375-21.patch | 196 --- .../expat/expat/CVE-2025-59375-22.patch | 37 - .../expat/expat/CVE-2025-59375-23.patch | 47 - .../expat/expat/CVE-2025-59375-24.patch | 36 - .../expat/expat/CVE-2026-24515-01.patch | 43 - .../expat/expat/CVE-2026-24515-02.patch | 117 -- .../expat/expat/CVE-2026-25210-01.patch | 27 - .../expat/expat/CVE-2026-25210-02.patch | 38 - .../expat/expat/CVE-2026-25210-03.patch | 28 - .../expat/expat/CVE-2026-32776.patch | 91 - .../expat/expat/CVE-2026-32777-01.patch | 49 - .../expat/expat/CVE-2026-32777-02.patch | 66 - .../expat/expat/CVE-2026-32778-01.patch | 91 - .../expat/expat/CVE-2026-32778-02.patch | 61 - .../expat/expat/CVE-2026-41080-01.patch | 50 - .../expat/expat/CVE-2026-41080-02.patch | 29 - .../expat/expat/CVE-2026-41080-03.patch | 467 ------ .../expat/expat/CVE-2026-45186-01.patch | 70 - .../expat/expat/CVE-2026-45186-02.patch | 318 ---- .../expat/expat/CVE-2026-45186-03.patch | 46 - .../expat/expat/CVE-2026-45186-04.patch | 32 - .../expat/expat/CVE-2026-45186-05.patch | 32 - .../expat/expat/CVE-2026-45186-06.patch | 87 - .../expat/expat/CVE-2026-45186-07.patch | 52 - .../expat/expat/CVE-2026-56132_p1.patch | 80 - .../expat/expat/CVE-2026-56132_p2.patch | 60 - .../expat/expat/CVE-2026-56132_p3.patch | 74 - .../expat/expat/CVE-2026-56132_p4.patch | 60 - .../expat/expat/CVE-2026-56132_p5.patch | 56 - .../expat/expat/CVE-2026-56403_p1.patch | 81 - .../expat/expat/CVE-2026-56403_p2.patch | 52 - .../expat/expat/CVE-2026-56404.patch | 45 - .../expat/expat/CVE-2026-56405.patch | 30 - .../expat/CVE-2026-56406-dependent.patch | 59 - .../expat/expat/CVE-2026-56406.patch | 34 - .../expat/expat/CVE-2026-56407.patch | 41 - .../expat/expat/CVE-2026-56408.patch | 29 - .../expat/expat/CVE-2026-56409.patch | 51 - .../expat/expat/CVE-2026-56410_p1.patch | 46 - .../expat/expat/CVE-2026-56410_p2.patch | 39 - .../expat/expat/CVE-2026-56411.patch | 50 - meta/recipes-core/expat/expat_2.6.4.bb | 104 -- meta/recipes-core/expat/expat_2.8.3.bb | 33 + .../glibc/glibc/0025-CVE-2026-6238-0001.patch | 59 + .../glibc/glibc/0026-CVE-2026-6238-0002.patch | 81 + .../glibc/glibc/0027-CVE-2026-6238-0003.patch | 58 + .../glibc/glibc/0028-CVE-2026-6238-0004.patch | 73 + .../glibc/glibc/0029-CVE-2026-6238-0005.patch | 69 + .../glibc/glibc/0030-CVE-2026-6238-0006.patch | 382 +++++ meta/recipes-core/glibc/glibc_2.39.bb | 6 + .../recipes-devtools/python/python-pyasn1.inc | 2 + .../python3-pyasn1/CVE-2026-30922.patch | 262 +++ .../python3-pyasn1/CVE-2026-59885.patch | 183 ++ .../atk/at-spi2-core_2.50.1.bb | 2 + .../files/CVE-2026-28417-regression_p1.patch | 78 + .../files/CVE-2026-28417-regression_p2.patch | 53 + meta/recipes-support/vim/vim.inc | 2 + 85 files changed, 1353 insertions(+), 7680 deletions(-) delete mode 100644 meta/recipes-core/expat/expat/0001-tests-Cover-indirect-entity-recursion.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-04.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-05.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-00.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-04.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-05.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-06.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-07.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-08.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-09.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-10.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-11.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-12.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-13.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-14.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-15.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-16.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-17.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-18.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-19.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-20.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-21.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-22.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-23.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-24.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-24515-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-24515-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-25210-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-25210-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-25210-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32776.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32777-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32777-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32778-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32778-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-41080-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-41080-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-41080-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-04.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-05.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-06.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-07.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p1.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p2.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p3.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p4.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p5.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56403_p1.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56403_p2.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56404.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56405.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56406-dependent.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56406.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56407.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56408.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56409.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56410_p1.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56410_p2.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56411.patch delete mode 100644 meta/recipes-core/expat/expat_2.6.4.bb create mode 100644 meta/recipes-core/expat/expat_2.8.3.bb create mode 100644 meta/recipes-core/glibc/glibc/0025-CVE-2026-6238-0001.patch create mode 100644 meta/recipes-core/glibc/glibc/0026-CVE-2026-6238-0002.patch create mode 100644 meta/recipes-core/glibc/glibc/0027-CVE-2026-6238-0003.patch create mode 100644 meta/recipes-core/glibc/glibc/0028-CVE-2026-6238-0004.patch create mode 100644 meta/recipes-core/glibc/glibc/0029-CVE-2026-6238-0005.patch create mode 100644 meta/recipes-core/glibc/glibc/0030-CVE-2026-6238-0006.patch create mode 100644 meta/recipes-devtools/python/python3-pyasn1/CVE-2026-30922.patch create mode 100644 meta/recipes-devtools/python/python3-pyasn1/CVE-2026-59885.patch create mode 100644 meta/recipes-support/vim/files/CVE-2026-28417-regression_p1.patch create mode 100644 meta/recipes-support/vim/files/CVE-2026-28417-regression_p2.patch
PATCH 1/8 glibc: Fix CVE-2026-6238
From: Deepesh Varatharajan <[email protected]>
Backport six commits from upstream glibc to fix CVE-2026-6238.
4ba0b79b95 resolv: Add test case tst-ns_sprintrr (bug 34033, bug 34069) a7b60d23bb resolv: Fix buffer overreads in ns_sprintrrf (CVE-2026-6238) cd0db208d5 resolv: Check for inet_ntop failure in ns_sprintrrf d58415eb17 resolv: Improve formatting of unknown records in ns_sprintrrf f69b7f95e3 resolv: Fix ns_sprintrrf formatting of class, type values (bug 34289) 360f352c9a resolv: Declare __p_class_syms, __p_type_syms for internal use
The upstream patch series [PATCH 0/5] contains five commits:
1/5: Update GLIBC-SA-2026-0012 to mention A6 records (doc only) 2/5: resolv: Check for inet_ntop failure in ns_sprintrrf 3/5: resolv: Remove incorrect parts of TSIG handling from ns_sprintrrf
(CVE-2026-5435)
4/5: resolv: Fix buffer overreads in ns_sprintrrf (CVE-2026-6238) 5/5: resolv: Add test case tst-ns_sprintrr (bug 34033, bug 34069)
For this backport:
- Patch 1/5 is skipped (documentation-only change to advisories, upstream glibc itself does not backport this to older releases)
- Patch 3/5 (CVE-2026-5435) is already patched in scarthgap sources
- Patches 2/5, 4/5, and 5/5 are backported as:
0028-CVE-2026-6238-0004.patch (inet_ntop failure check) 0029-CVE-2026-6238-0005.patch (buffer overread fix - CVE-2026-6238) 0030-CVE-2026-6238-0006.patch (test case for bug 34033, bug 34069)
However, the test case (tst-ns_sprintrr) from patch 5/5 failed on scarthgap's glibc 2.39 due to missing prerequisite commits. Three additional patches were backported to resolve the test failure:
0025-CVE-2026-6238-0001.patch (Declare __p_class_syms, __p_type_syms for internal) 0026-CVE-2026-6238-0002.patch (Fix ns_sprintrrf formatting of class, type values) 0027-CVE-2026-6238-0003.patch (Improve formatting of unknown records in ns_sprintrrf)
CVE-2026-6238 fixes buffer overreads in ns_sprintrrf affecting A6 and LOC record handling. The vulnerable LOC record handling was introduced before glibc 2.0, while A6 record handling was added in glibc 2.7.
Reference:
https://inbox.sourceware.org/libc-alpha/[email protected]/
https://nvd.nist.gov/vuln/detail/CVE-2026-6238
https://sourceware.org/bugzilla/show_bug.cgi?id=34069
Testing Results:
Before After Diff PASS 4896 4897 +1 XPASS 4 4 0 FAIL 372 372 0 XFAIL 16 16 0 UNSUPPORTED 224 224 0
Changes in testcases:
testcase-name before after
resolv/tst-ns_sprintrr(new) - PASS
commit - 4ba0b79b95 resolv: Add test case tst-ns_sprintrr (bug 34033, bug 34069) +PASS: resolv/tst-ns_sprintrr
--- .../glibc/glibc/0025-CVE-2026-6238-0001.patch | 59 +++ .../glibc/glibc/0026-CVE-2026-6238-0002.patch | 81 ++++ .../glibc/glibc/0027-CVE-2026-6238-0003.patch | 58 +++ .../glibc/glibc/0028-CVE-2026-6238-0004.patch | 73 ++++ .../glibc/glibc/0029-CVE-2026-6238-0005.patch | 69 ++++ .../glibc/glibc/0030-CVE-2026-6238-0006.patch | 382 ++++++++++++++++++ meta/recipes-core/glibc/glibc_2.39.bb | 6 + 7 files changed, 728 insertions(+) create mode 100644 meta/recipes-core/glibc/glibc/0025-CVE-2026-6238-0001.patch create mode 100644 meta/recipes-core/glibc/glibc/0026-CVE-2026-6238-0002.patch create mode 100644 meta/recipes-core/glibc/glibc/0027-CVE-2026-6238-0003.patch create mode 100644 meta/recipes-core/glibc/glibc/0028-CVE-2026-6238-0004.patch create mode 100644 meta/recipes-core/glibc/glibc/0029-CVE-2026-6238-0005.patch create mode 100644 meta/recipes-core/glibc/glibc/0030-CVE-2026-6238-0006.patch
meta/recipes-core/glibc/glibc/0025-CVE-2026-6238-0001.patch new file +59 -0
@@ -0,0 +1,59 @@ +From 360f352c9a6da545d798ef3015e73ca114f0d230 Mon Sep 17 00:00:00 2001 +From: Florian Weimer <[email protected]> +Date: Fri, 19 Jun 2026 18:22:20 +0200 +Subject: [PATCH] resolv: Declare __p_class_syms, __p_type_syms for internal + use + +Reviewed-by: Carlos O'Donell <[email protected]> +Reviewed-by: Adhemerval Zanella <[email protected]> + +CVE: CVE-2026-6238 +Upstream-Status: Backport [https://sourceware.org/git/?p=glibc.git;a=patch;h=360f352c9a6da545d798ef3015e73ca114f0d230] + +Signed-off-by: Deepesh Varatharajan <[email protected]> +--- + include/resolv.h | 5 +++++ + resolv/res_debug.c | 4 ---- + 2 files changed, 5 insertions(+), 4 deletions(-) + +diff --git a/include/resolv.h b/include/resolv.h +index 4dbbac38..d5ad9994 100644 +--- a/include/resolv.h ++++ b/include/resolv.h +@@ -70,6 +70,11 @@ libc_hidden_proto (__libc_res_nameinquery) + extern __typeof (__res_queriesmatch) __libc_res_queriesmatch; + libc_hidden_proto (__libc_res_queriesmatch) + ++extern const struct res_sym __p_class_syms[]; ++libresolv_hidden_proto (__p_class_syms) ++extern const struct res_sym __p_type_syms[]; ++libresolv_hidden_proto (__p_type_syms) ++ + /* Variant of res_hnok which operates on binary (but uncompressed) names. */ + bool __res_binary_hnok (const unsigned char *dn) attribute_hidden; + +diff --git a/resolv/res_debug.c b/resolv/res_debug.c +index dab5283b..6f03e414 100644 +--- a/resolv/res_debug.c ++++ b/resolv/res_debug.c +@@ -389,8 +389,6 @@ p_fqname(const u_char *cp, const u_char *msg, FILE *file) { + * that C_ANY is a qclass but not a class. (You can ask for records of class + * C_ANY, but you can't have any records of that class in the database.) + */ +-extern const struct res_sym __p_class_syms[]; +-libresolv_hidden_proto (__p_class_syms) + const struct res_sym __p_class_syms[] = { + {C_IN, (char *) "IN"}, + {C_CHAOS, (char *) "CHAOS"}, +@@ -425,8 +423,6 @@ const struct res_sym __p_update_section_syms[] attribute_hidden = { + * Names of RR types and qtypes. The list is incomplete because its + * size is part of the ABI. + */ +-extern const struct res_sym __p_type_syms[]; +-libresolv_hidden_proto (__p_type_syms) + const struct res_sym __p_type_syms[] = { + {ns_t_a, (char *) "A", (char *) "address"}, + {ns_t_ns, (char *) "NS", (char *) "name server"}, +-- +2.49.0 +
meta/recipes-core/glibc/glibc/0026-CVE-2026-6238-0002.patch new file +81 -0
81 lines not on this page · raw message
meta/recipes-core/glibc/glibc/0027-CVE-2026-6238-0003.patch new file +58 -0
58 lines not on this page · raw message
meta/recipes-core/glibc/glibc/0028-CVE-2026-6238-0004.patch new file +73 -0
73 lines not on this page · raw message
meta/recipes-core/glibc/glibc/0029-CVE-2026-6238-0005.patch new file +69 -0
69 lines not on this page · raw message
meta/recipes-core/glibc/glibc/0030-CVE-2026-6238-0006.patch new file +382 -0
382 lines not on this page · raw message
meta/recipes-core/glibc/glibc_2.39.bb +6 -0
@@ -57,6 +57,12 @@ SRC_URI = "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \ file://0023-qemu-stale-process.patch \ file://0001-stdlib-Add-single-threaded-fast-path-to-rand.patch \ file://0024-CVE-2026-5435.patch \ + file://0025-CVE-2026-6238-0001.patch \ + file://0026-CVE-2026-6238-0002.patch \ + file://0027-CVE-2026-6238-0003.patch \ + file://0028-CVE-2026-6238-0004.patch \ + file://0029-CVE-2026-6238-0005.patch \ + file://0030-CVE-2026-6238-0006.patch \ " S = "${WORKDIR}/git" B = "${WORKDIR}/build-${TARGET_SYS}"
PATCH 2/8 expat: upgrade 2.6.4 -> 2.8.3, exception security update
In reply to Yoann CongalFrom: Jakub Szczudlo (Nokia) <[email protected]>
Unusual upgrade for expat to version 2.8.3
This is because there is a lot of CVEs and some are bigger than 20+ commits so maintaining them is difficult
In new version there are fixes for CVE-2026-50219, CVE-2026-56131, CVE-2026-56412, CVE-2026-72522 that was not backported yet
No braking ABI changes only 3 functions was added:
3 Added functions:
[A] 'function XML_Bool XML_SetAllocTrackerActivationThreshold(XML_Parser, long long unsigned int)' {XML_SetAllocTrackerActivationThreshold}
[A] 'function XML_Bool XML_SetAllocTrackerMaximumAmplification(XML_Parser, float)' {XML_SetAllocTrackerMaximumAmplification}
[A] 'function XML_Bool XML_SetHashSalt16Bytes(XML_Parser, const uint8_t*)' {XML_SetHashSalt16Bytes}
SONAME name stays the same as it was before - libexpat.so.1 Build all find package that depends on expat:
python3-xml fontconfig python3-xmltodict apr-util libxml-parser-perl exiv2 graphviz libdbus-c++ libwmf log4c neon poco polkit sdbus-c++ sdbus-c++-tools wbxml2 apache2 lftp unbound wireshark libmusicbrainz mpd gegl
Tested using ptests for python3-xmltodict apr-util libxml-parser-perl and expat itself
There is already planned expat 2.8.4 release but CVE fix there are small and thus maintainable
Changelog notes here:
https://github.com/libexpat/libexpat/blob/R_2_8_3/expat/Changes
[YC: CVE-2026-72522 was ignored in the meantime, I removed the CVE_STATUS line]
--- ...ests-Cover-indirect-entity-recursion.patch | 103 -- .../expat/expat/CVE-2024-8176-01.patch | 1477 ----------------- .../expat/expat/CVE-2024-8176-02.patch | 248 --- .../expat/expat/CVE-2024-8176-03.patch | 35 - .../expat/expat/CVE-2024-8176-04.patch | 115 -- .../expat/expat/CVE-2024-8176-05.patch | 78 - .../expat/expat/CVE-2025-59375-00.patch | 52 - .../expat/expat/CVE-2025-59375-01.patch | 48 - .../expat/expat/CVE-2025-59375-02.patch | 109 -- .../expat/expat/CVE-2025-59375-03.patch | 127 -- .../expat/expat/CVE-2025-59375-04.patch | 62 - .../expat/expat/CVE-2025-59375-05.patch | 64 - .../expat/expat/CVE-2025-59375-06.patch | 68 - .../expat/expat/CVE-2025-59375-07.patch | 52 - .../expat/expat/CVE-2025-59375-08.patch | 577 ------- .../expat/expat/CVE-2025-59375-09.patch | 43 - .../expat/expat/CVE-2025-59375-10.patch | 54 - .../expat/expat/CVE-2025-59375-11.patch | 66 - .../expat/expat/CVE-2025-59375-12.patch | 58 - .../expat/expat/CVE-2025-59375-13.patch | 309 ---- .../expat/expat/CVE-2025-59375-14.patch | 122 -- .../expat/expat/CVE-2025-59375-15.patch | 70 - .../expat/expat/CVE-2025-59375-16.patch | 146 -- .../expat/expat/CVE-2025-59375-17.patch | 28 - .../expat/expat/CVE-2025-59375-18.patch | 74 - .../expat/expat/CVE-2025-59375-19.patch | 103 -- .../expat/expat/CVE-2025-59375-20.patch | 285 ---- .../expat/expat/CVE-2025-59375-21.patch | 196 --- .../expat/expat/CVE-2025-59375-22.patch | 37 - .../expat/expat/CVE-2025-59375-23.patch | 47 - .../expat/expat/CVE-2025-59375-24.patch | 36 - .../expat/expat/CVE-2026-24515-01.patch | 43 - .../expat/expat/CVE-2026-24515-02.patch | 117 -- .../expat/expat/CVE-2026-25210-01.patch | 27 - .../expat/expat/CVE-2026-25210-02.patch | 38 - .../expat/expat/CVE-2026-25210-03.patch | 28 - .../expat/expat/CVE-2026-32776.patch | 91 - .../expat/expat/CVE-2026-32777-01.patch | 49 - .../expat/expat/CVE-2026-32777-02.patch | 66 - .../expat/expat/CVE-2026-32778-01.patch | 91 - .../expat/expat/CVE-2026-32778-02.patch | 61 - .../expat/expat/CVE-2026-41080-01.patch | 50 - .../expat/expat/CVE-2026-41080-02.patch | 29 - .../expat/expat/CVE-2026-41080-03.patch | 467 ------ .../expat/expat/CVE-2026-45186-01.patch | 70 - .../expat/expat/CVE-2026-45186-02.patch | 318 ---- .../expat/expat/CVE-2026-45186-03.patch | 46 - .../expat/expat/CVE-2026-45186-04.patch | 32 - .../expat/expat/CVE-2026-45186-05.patch | 32 - .../expat/expat/CVE-2026-45186-06.patch | 87 - .../expat/expat/CVE-2026-45186-07.patch | 52 - .../expat/expat/CVE-2026-56132_p1.patch | 80 - .../expat/expat/CVE-2026-56132_p2.patch | 60 - .../expat/expat/CVE-2026-56132_p3.patch | 74 - .../expat/expat/CVE-2026-56132_p4.patch | 60 - .../expat/expat/CVE-2026-56132_p5.patch | 56 - .../expat/expat/CVE-2026-56403_p1.patch | 81 - .../expat/expat/CVE-2026-56403_p2.patch | 52 - .../expat/expat/CVE-2026-56404.patch | 45 - .../expat/expat/CVE-2026-56405.patch | 30 - .../expat/CVE-2026-56406-dependent.patch | 59 - .../expat/expat/CVE-2026-56406.patch | 34 - .../expat/expat/CVE-2026-56407.patch | 41 - .../expat/expat/CVE-2026-56408.patch | 29 - .../expat/expat/CVE-2026-56409.patch | 51 - .../expat/expat/CVE-2026-56410_p1.patch | 46 - .../expat/expat/CVE-2026-56410_p2.patch | 39 - .../expat/expat/CVE-2026-56411.patch | 50 - meta/recipes-core/expat/expat_2.6.4.bb | 104 -- meta/recipes-core/expat/expat_2.8.3.bb | 33 + 70 files changed, 33 insertions(+), 7674 deletions(-) delete mode 100644 meta/recipes-core/expat/expat/0001-tests-Cover-indirect-entity-recursion.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-04.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2024-8176-05.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-00.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-04.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-05.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-06.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-07.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-08.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-09.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-10.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-11.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-12.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-13.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-14.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-15.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-16.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-17.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-18.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-19.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-20.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-21.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-22.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-23.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-24.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-24515-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-24515-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-25210-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-25210-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-25210-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32776.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32777-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32777-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32778-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-32778-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-41080-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-41080-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-41080-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-01.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-02.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-03.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-04.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-05.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-06.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-45186-07.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p1.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p2.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p3.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p4.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p5.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56403_p1.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56403_p2.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56404.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56405.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56406-dependent.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56406.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56407.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56408.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56409.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56410_p1.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56410_p2.patch delete mode 100644 meta/recipes-core/expat/expat/CVE-2026-56411.patch delete mode 100644 meta/recipes-core/expat/expat_2.6.4.bb create mode 100644 meta/recipes-core/expat/expat_2.8.3.bb
meta/recipes-core/expat/expat/0001-tests-Cover-indirect-entity-recursion.patch deleted +0 -103
@@ -1,103 +0,0 @@ -From 3d5fdbb44e80ed789e4f6510542d77d6284fbd0e Mon Sep 17 00:00:00 2001 -From: Sebastian Pipping <[email protected]> -Date: Sat, 23 Nov 2024 14:20:21 +0100 -Subject: [PATCH] tests: Cover indirect entity recursion - -Upstream-Status: Backport [https://github.com/libexpat/libexpat/commit/3d5fdbb44e80ed789e4f6510542d77d6284fbd0e] -Signed-off-by: Peter Marko <[email protected]> ---- - expat/tests/basic_tests.c | 74 +++++++++++++++++++++++++++++++++++++++ - 1 file changed, 74 insertions(+) - -diff --git a/expat/tests/basic_tests.c b/expat/tests/basic_tests.c -index d38b8fd1..d2306772 100644 ---- a/expat/tests/basic_tests.c -+++ b/expat/tests/basic_tests.c -@@ -1202,6 +1202,79 @@ START_TEST(test_wfc_no_recursive_entity_refs) { - } - END_TEST - -+START_TEST(test_no_indirectly_recursive_entity_refs) { -+ struct TestCase { -+ const char *doc; -+ bool usesParameterEntities; -+ }; -+ -+ const struct TestCase cases[] = { -+ // general entity + character data -+ {"<!DOCTYPE a [\n" -+ " <!ENTITY e1 '&e2;'>\n" -+ " <!ENTITY e2 '&e1;'>\n" -+ "]><a>&e2;</a>\n", -+ false}, -+ -+ // general entity + attribute value -+ {"<!DOCTYPE a [\n" -+ " <!ENTITY e1 '&e2;'>\n" -+ " <!ENTITY e2 '&e1;'>\n" -+ "]><a k1='&e2;' />\n", -+ false}, -+ -+ // parameter entity -+ {"<!DOCTYPE doc [\n" -+ " <!ENTITY % p1 '%p2;'>\n" -+ " <!ENTITY % p2 '%p1;'>\n" -+ " <!ENTITY % define_g \"<!ENTITY g '%p2;'>\">\n" -+ " %define_g;\n" -+ "]>\n" -+ "<doc/>\n", -+ true}, -+ }; -+ for (size_t i = 0; i < sizeof(cases) / sizeof(cases[0]); i++) { -+ const char *const doc = cases[i].doc; -+ const bool usesParameterEntities = cases[i].usesParameterEntities; -+ -+ set_subtest("[%i] %s", (int)i, doc); -+ -+#ifdef XML_DTD // both GE and DTD -+ const bool rejection_expected = true; -+#elif XML_GE == 1 // GE but not DTD -+ const bool rejection_expected = ! usesParameterEntities; -+#else // neither DTD nor GE -+ const bool rejection_expected = false; -+#endif -+ -+ XML_Parser parser = XML_ParserCreate(NULL); -+ -+#ifdef XML_DTD -+ if (usesParameterEntities) { -+ assert_true( -+ XML_SetParamEntityParsing(parser, XML_PARAM_ENTITY_PARSING_ALWAYS) -+ == 1); -+ } -+#else -+ UNUSED_P(usesParameterEntities); -+#endif // XML_DTD -+ -+ const enum XML_Status status -+ = _XML_Parse_SINGLE_BYTES(parser, doc, (int)strlen(doc), -+ /*isFinal*/ XML_TRUE); -+ -+ if (rejection_expected) { -+ assert_true(status == XML_STATUS_ERROR); -+ assert_true(XML_GetErrorCode(parser) == XML_ERROR_RECURSIVE_ENTITY_REF); -+ } else { -+ assert_true(status == XML_STATUS_OK); -+ } -+ -+ XML_ParserFree(parser); -+ } -+} -+END_TEST -+ - START_TEST(test_recursive_external_parameter_entity_2) { - struct TestCase { - const char *doc; -@@ -5969,6 +6042,7 @@ make_basic_test_case(Suite *s) { - tcase_add_test(tc_basic, test_not_standalone_handler_reject); - tcase_add_test(tc_basic, test_not_standalone_handler_accept); - tcase_add_test__if_xml_ge(tc_basic, test_wfc_no_recursive_entity_refs); -+ tcase_add_test(tc_basic, test_no_indirectly_recursive_entity_refs); - tcase_add_test__ifdef_xml_dtd(tc_basic, test_ext_entity_invalid_parse); - tcase_add_test__if_xml_ge(tc_basic, test_dtd_default_handling); - tcase_add_test(tc_basic, test_dtd_attr_handling);
meta/recipes-core/expat/expat/CVE-2024-8176-01.patch deleted +0 -1477
1,477 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2024-8176-02.patch deleted +0 -248
248 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2024-8176-03.patch deleted +0 -35
@@ -1,35 +0,0 @@ -From ba80428c2207259103b73871d447dee34755340c Mon Sep 17 00:00:00 2001 -From: =?UTF-8?q?Berkay=20Eren=20=C3=9Cr=C3=BCn?= <[email protected]> -Date: Tue, 23 Sep 2025 11:22:14 +0200 -Subject: [PATCH] lib: Fix detection of asynchronous tags in entities - -According to the XML standard, tags must be closed within the same -element in which they are opened. Since the change of the entity -processing method in version 2.7.0, violations of this rule have not -been handled correctly for entities. - -This commit adds the required checks to detect any violations and -restores the correct behaviour. - -CVE: CVE-2024-8176 -Upstream-Status: Backport [https://github.com/libexpat/libexpat/pull/1059] -Signed-off-by: Peter Marko <[email protected]> ---- - lib/xmlparse.c | 4 ++++ - 1 file changed, 4 insertions(+) - -diff --git a/lib/xmlparse.c b/lib/xmlparse.c -index ce29ab6f..ba4e3c48 100644 ---- a/lib/xmlparse.c -+++ b/lib/xmlparse.c -@@ -6087,6 +6087,10 @@ internalEntityProcessor(XML_Parser parser, const char *s, const char *end, - // process its possible inner entities (which are added to the - // m_openInternalEntities during doProlog or doContent calls above) - entity->hasMore = XML_FALSE; -+ if (! entity->is_param -+ && (openEntity->startTagLevel != parser->m_tagLevel)) { -+ return XML_ERROR_ASYNC_ENTITY; -+ } - triggerReenter(parser); - return result; - } // End of entity processing, "if" block will return here
meta/recipes-core/expat/expat/CVE-2024-8176-04.patch deleted +0 -115
115 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2024-8176-05.patch deleted +0 -78
78 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-00.patch deleted +0 -52
52 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-01.patch deleted +0 -48
48 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-02.patch deleted +0 -109
109 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-03.patch deleted +0 -127
127 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-04.patch deleted +0 -62
62 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-05.patch deleted +0 -64
64 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-06.patch deleted +0 -68
68 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-07.patch deleted +0 -52
52 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-08.patch deleted +0 -577
362 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-09.patch deleted +0 -43
43 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-10.patch deleted +0 -54
54 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-11.patch deleted +0 -66
66 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-12.patch deleted +0 -58
58 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-13.patch deleted +0 -309
309 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-14.patch deleted +0 -122
122 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-15.patch deleted +0 -70
70 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-16.patch deleted +0 -146
146 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-17.patch deleted +0 -28
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2025-59375-18.patch deleted +0 -74
74 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-19.patch deleted +0 -103
103 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-20.patch deleted +0 -285
285 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-21.patch deleted +0 -196
196 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-22.patch deleted +0 -37
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2025-59375-23.patch deleted +0 -47
47 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-24.patch deleted +0 -36
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-24515-01.patch deleted +0 -43
43 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-24515-02.patch deleted +0 -117
117 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-25210-01.patch deleted +0 -27
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-25210-02.patch deleted +0 -38
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-25210-03.patch deleted +0 -28
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-32776.patch deleted +0 -91
91 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-32777-01.patch deleted +0 -49
49 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-32777-02.patch deleted +0 -66
66 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-32778-01.patch deleted +0 -91
91 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-32778-02.patch deleted +0 -61
61 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-41080-01.patch deleted +0 -50
50 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-41080-02.patch deleted +0 -29
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-41080-03.patch deleted +0 -467
467 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-45186-01.patch deleted +0 -70
70 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-45186-02.patch deleted +0 -318
318 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-45186-03.patch deleted +0 -46
46 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-45186-04.patch deleted +0 -32
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-45186-05.patch deleted +0 -32
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-45186-06.patch deleted +0 -87
87 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-45186-07.patch deleted +0 -52
52 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56132_p1.patch deleted +0 -80
80 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56132_p2.patch deleted +0 -60
60 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56132_p3.patch deleted +0 -74
74 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56132_p4.patch deleted +0 -60
60 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56132_p5.patch deleted +0 -56
56 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56403_p1.patch deleted +0 -81
81 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56403_p2.patch deleted +0 -52
52 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56404.patch deleted +0 -45
45 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56405.patch deleted +0 -30
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-56406-dependent.patch deleted +0 -59
59 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56406.patch deleted +0 -34
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-56407.patch deleted +0 -41
41 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56408.patch deleted +0 -29
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-56409.patch deleted +0 -51
51 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56410_p1.patch deleted +0 -46
46 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2026-56410_p2.patch deleted +0 -39
Lines of this file are not shown. View the raw message.
meta/recipes-core/expat/expat/CVE-2026-56411.patch deleted +0 -50
50 lines not on this page · raw message
meta/recipes-core/expat/expat_2.6.4.bb deleted +0 -104
104 lines not on this page · raw message
meta/recipes-core/expat/expat_2.8.3.bb new file +33 -0
Lines of this file are not shown. View the raw message.
The rest of this diff is not shown. View the raw message.
Part of the diff is not shown here. View the raw message.
PATCH 3/8 vim: Fix CVE-2026-28417 regressions
In reply to Yoann CongalFrom: Devansh Patel <[email protected]>
The older Vim patch 9.2.0073 fixed CVE-2026-28417 by tightening netrw hostname validation. That CVE fix requires two regression patches because it rejects valid hostnames that include an optional port or an underscore.
Backport Vim patches 9.2.0089 and 9.2.0553 in that order. They restore optional-port and underscore handling while retaining the stricter validation introduced by the original CVE fix.
Scarthgap's Vim 9.1.1683 source does not contain test_plugin_netrw.vim, so the upstream test hunks are omitted. The src/version.c hunks are also omitted because this backport does not change the recipe version or Vim's upstream patch-number table.
[1] https://github.com/vim/vim/commit/79348dbbc09332130f4c86045e1541d68514fcc1
[2] https://github.com/vim/vim/commit/a6198523fb28a50d96945458792cdb4787d3cdda
[3] https://github.com/vim/vim/commit/93d177cd2b69bac58fc51a5a514d7bc71e264b11
[4] https://github.com/vim/vim/security/advisories/GHSA-m3xh-9434-g336
--- .../files/CVE-2026-28417-regression_p1.patch | 78 +++++++++++++++++++ .../files/CVE-2026-28417-regression_p2.patch | 53 +++++++++++++ meta/recipes-support/vim/vim.inc | 2 + 3 files changed, 133 insertions(+) create mode 100644 meta/recipes-support/vim/files/CVE-2026-28417-regression_p1.patch create mode 100644 meta/recipes-support/vim/files/CVE-2026-28417-regression_p2.patch
meta/recipes-support/vim/files/CVE-2026-28417-regression_p1.patch new file +78 -0
@@ -0,0 +1,78 @@ +From a6e9906380af2b51ea4b77234ef77b14cc712f2c Mon Sep 17 00:00:00 2001 +From: Miguel Barro <[email protected]> +Date: Sun, 1 Mar 2026 19:32:29 +0000 +Subject: [PATCH] patch 9.2.0089: netrw: does not take port into account in + hostname validation + +Problem: netrw: does not take port into account in hostname validation + (after v9.2.0073) +Solution: Update hostname validation check and test for an optional port + number (Miguel Barro) + +closes: #19533 + +CVE: CVE-2026-28417 +Upstream-Status: Backport [https://github.com/vim/vim/commit/a6198523fb28a50d96945458792cdb4787d3cdda] + +Backport Changes: +- Omitted src/testdir/test_plugin_netrw.vim because this test file is not + present in the Vim 9.1.1683 source used by Scarthgap. +- Omitted src/version.c because this backport does not change the recipe's + Vim version or its upstream patch-number table. + +Signed-off-by: Miguel Barro <[email protected]> +Signed-off-by: Christian Brabandt <[email protected]> +(cherry picked from commit a6198523fb28a50d96945458792cdb4787d3cdda) +Signed-off-by: Devansh Patel <[email protected]> +--- + runtime/pack/dist/opt/netrw/autoload/netrw.vim | 18 +++++++++++------- + 1 file changed, 11 insertions(+), 7 deletions(-) + +diff --git a/runtime/pack/dist/opt/netrw/autoload/netrw.vim b/runtime/pack/dist/opt/netrw/autoload/netrw.vim +index 1b790d250..69eababf1 100644 +--- a/runtime/pack/dist/opt/netrw/autoload/netrw.vim ++++ b/runtime/pack/dist/opt/netrw/autoload/netrw.vim +@@ -6,6 +6,7 @@ + " 2025 Aug 07 by Vim Project (netrw#BrowseX() distinguishes remote files #17794) + " 2025 Aug 22 by Vim Project netrw#Explore handle terminal correctly #18069 + " 2026 Feb 27 by Vim Project Make the hostname validation more strict ++" 2026 Mar 01 by Vim Project include portnumber in hostname checking #19533 + " Copyright: Copyright (C) 2016 Charles E. Campbell {{{1 + " Permission is hereby granted to use and distribute this code, + " with or without modifications, provided that this copyright +@@ -2575,7 +2576,8 @@ endfunction + + " s:NetrwValidateHostname: Validate that the hostname is valid {{{2 + " Input: +-" hostname, may include an optional username, e.g. user@hostname ++" hostname, may include an optional username and port number, e.g. ++" user@hostname:port + " allow a alphanumeric hostname or an IPv(4/6) address + " Output: + " true if g:netrw_machine is valid according to RFC1123 #Section 2 +@@ -2584,17 +2586,19 @@ function s:NetrwValidateHostname(hostname) + let user_pat = '\%([a-zA-Z0-9._-]\+@\)\?' + " Hostname: 1-64 chars, alphanumeric/dots/hyphens. + " No underscores. No leading/trailing dots/hyphens. +- let host_pat = '[a-zA-Z0-9]\%([-a-zA-Z0-9.]{,62}[a-zA-Z0-9]\)\?$' ++ let host_pat = '[a-zA-Z0-9]\%([-a-zA-Z0-9.]\{0,62}[a-zA-Z0-9]\)\?' ++ " Port: 16 bit unsigned integer ++ let port_pat = '\%(:\d\{1,5\}\)\?$' + + " IPv4: 1-3 digits separated by dots +- let ipv4_pat = '\%(\d\{1,3}\.\)\{3\}\d\{1,3\}$' ++ let ipv4_pat = '\%(\d\{1,3}\.\)\{3\}\d\{1,3\}' + + " IPv6: Hex, colons, and optional brackets +- let ipv6_pat = '\[\?\%([a-fA-F0-9:]\{2,}\)\+\]\?$' ++ let ipv6_pat = '\[\?\%([a-fA-F0-9:]\{2,}\)\+\]\?' + +- return a:hostname =~? '^'.user_pat.host_pat || +- \ a:hostname =~? '^'.user_pat.ipv4_pat || +- \ a:hostname =~? '^'.user_pat.ipv6_pat ++ return a:hostname =~? '^'.user_pat.host_pat.port_pat || ++ \ a:hostname =~? '^'.user_pat.ipv4_pat.port_pat || ++ \ a:hostname =~? '^'.user_pat.ipv6_pat.port_pat + endfunction + + " NetUserPass: set username and password for subsequent ftp transfer {{{2
meta/recipes-support/vim/files/CVE-2026-28417-regression_p2.patch new file +53 -0
53 lines not on this page · raw message
meta/recipes-support/vim/vim.inc +2 -0
@@ -30,6 +30,8 @@ SRC_URI = "git://github.com/vim/vim.git;branch=master;protocol=https \ file://CVE-2026-28421.patch \ file://CVE-2026-32249.patch \ file://CVE-2026-28417.patch \ + file://CVE-2026-28417-regression_p1.patch \ + file://CVE-2026-28417-regression_p2.patch \ file://CVE-2026-45130.patch \ file://CVE-2026-46483.patch \ file://CVE-2026-28420.patch \
PATCH 4/8 at-spi2-core: RDEPENDS on gsettings-desktop-schemas
In reply to Yoann CongalFrom: Tim Orling <[email protected]>
at-spi-bus-launcher aborts when no compiled GSettings schema is present.
This has been a fatal error since [1]:
"26f75dc0 bus: Abort if we cannot get the default GSettingsSchemaSource"
[1] https://gitlab.gnome.org/GNOME/at-spi2-core/-/commit/26f75dc00eb16ccec89561aefe15f4036d45b4ec
--- meta/recipes-support/atk/at-spi2-core_2.50.1.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-support/atk/at-spi2-core_2.50.1.bb +2 -0
@@ -25,6 +25,8 @@ DEPENDS = " \ PROVIDES += "atk at-spi2-atk" RPROVIDES:${PN} += "atk at-spi2-atk" +RDEPENDS:${PN}:append:class-target = " gsettings-desktop-schemas" + inherit meson gi-docgen gettext systemd pkgconfig upstream-version-is-even gobject-introspection EXTRA_OEMESON = " -Dsystemd_user_dir=${systemd_user_unitdir} \
PATCH 5/8 sstate: Update mtime/atime for sig/siginfo files in sstate_checkhashes()
In reply to Yoann CongalFrom: Richard Purdie <[email protected]>
If we touch sstatefile, we should also touch any .sig/.siginfo file if we can. We try and keep them both updated with accesses so one isn't removed without the other and they stay consistent.
[YOCTO #15289]
--- meta/classes-global/sstate.bbclass | 3 +++ 1 file changed, 3 insertions(+)
meta/classes-global/sstate.bbclass +3 -0
@@ -978,6 +978,9 @@ def sstate_checkhashes(sq_data, d, siginfo=False, currentcount=0, summary=True, if os.path.exists(sstatefile): oe.utils.touch(sstatefile) + for ext in ['.sig', '.siginfo']: + if os.path.exists(sstatefile + ext): + oe.utils.touch(sstatefile + ext) found.add(tid) bb.debug(2, "SState: Found valid sstate file %s" % sstatefile) else:
PATCH 6/8 sstate: Update unpack touch code to be consistent
In reply to Yoann CongalFrom: Richard Purdie <[email protected]>
When we unpack sstate files, we want to update the mtime+atime of the sstate object and any sig/siginfo files, both for the files themselves and symlinks.
The logic was getting a bit hard to follow and wasn't entirely consistent with only a time in some cases.
Clean it up and be consistent for all the files.
--- meta/classes-global/sstate.bbclass | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
meta/classes-global/sstate.bbclass +7 -6
@@ -932,12 +932,13 @@ sstate_unpack_package () { fi tar -I "$ZSTD" -xvpf ${SSTATE_PKG} - # update .siginfo atime on local/NFS mirror if it is a symbolic link - [ ! -h ${SSTATE_PKG}.siginfo ] || [ ! -e ${SSTATE_PKG}.siginfo ] || touch -a ${SSTATE_PKG}.siginfo 2>/dev/null || true - # update each symbolic link instead of any referenced file - touch --no-dereference ${SSTATE_PKG} 2>/dev/null || true - [ ! -e ${SSTATE_PKG}.sig ] || touch --no-dereference ${SSTATE_PKG}.sig 2>/dev/null || true - [ ! -e ${SSTATE_PKG}.siginfo ] || touch --no-dereference ${SSTATE_PKG}.siginfo 2>/dev/null || true + + # Update both any file and any symlink pointing to the file for sigs as well as the file + for file in ${SSTATE_PKG} ${SSTATE_PKG}.sig ${SSTATE_PKG}.siginfo + do + [ ! -e $file ] || touch $file 2>/dev/null || true + [ ! -e $file ] || touch --no-dereference $file 2>/dev/null || true + done } BB_HASHCHECK_FUNCTION = "sstate_checkhashes"
PATCH 7/8 python3-pyasn1: fix CVE-2026-30922
In reply to Yoann CongalFrom: Yogita Urade <[email protected]>
This patch applies upstream fix for CVE-2026-30922 as referenced in [2], using the upstream commit identified in [1].
[1] https://github.com/pyasn1/pyasn1/commit/25ad481c19fdb006e20485ef3fc2e5b3eff30ef0
[2] https://nvd.nist.gov/vuln/detail/CVE-2026-30922
--- .../recipes-devtools/python/python-pyasn1.inc | 1 + .../python3-pyasn1/CVE-2026-30922.patch | 262 ++++++++++++++++++ 2 files changed, 263 insertions(+) create mode 100644 meta/recipes-devtools/python/python3-pyasn1/CVE-2026-30922.patch
meta/recipes-devtools/python/python-pyasn1.inc +1 -0
@@ -21,6 +21,7 @@ SRC_URI += " \ file://CVE-2026-23490.patch \ file://CVE-2026-59886.patch \ file://CVE-2026-59884.patch \ + file://CVE-2026-30922.patch \ " RDEPENDS:${PN}-ptest += " \
meta/recipes-devtools/python/python3-pyasn1/CVE-2026-30922.patch new file +262 -0
262 lines not on this page · raw message
PATCH 8/8 python3-pyasn1: fix CVE-2026-59885
In reply to Yoann CongalFrom: Yogita Urade <[email protected]>
This patch applies the upstream fix as referenced in [2], using the commit shown in [1].
[1] https://github.com/pyasn1/pyasn1/commit/45bdb19eb7df4b3780fe9c912c63e99bffc39dd9
[2] https://nvd.nist.gov/vuln/detail/CVE-2026-59885
--- .../recipes-devtools/python/python-pyasn1.inc | 1 + .../python3-pyasn1/CVE-2026-59885.patch | 183 ++++++++++++++++++ 2 files changed, 184 insertions(+) create mode 100644 meta/recipes-devtools/python/python3-pyasn1/CVE-2026-59885.patch
meta/recipes-devtools/python/python-pyasn1.inc +1 -0
@@ -22,6 +22,7 @@ SRC_URI += " \ file://CVE-2026-59886.patch \ file://CVE-2026-59884.patch \ file://CVE-2026-30922.patch \ + file://CVE-2026-59885.patch \ " RDEPENDS:${PN}-ptest += " \
meta/recipes-devtools/python/python3-pyasn1/CVE-2026-59885.patch new file +183 -0
183 lines not on this page · raw message