Patch review
cover Patch review
Please review this set of changes for scarthgap and have comments back by end of day Thursday, October 30
Passed a-full on the autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2645
with the exception of the meta-aws test, which failed due to a meta-aws commit changing the distro from poky-agl to agl
The following changes since commit 649147913e89cd8f7390cb17cd0be94c9710ffa6:
oeqa/runtime/ping: don't bother trying to ping localhost (2025-10-17 07:47:32 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/scarthgap-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/scarthgap-nut
Anders Heimer (1):
libpam: mark CVE-2025-6018 as not applicable
Daniel Semkowicz (1):
gstreamer1.0-plugins-bad: fix buffer allocation fail for v4l2codecs
Martin Jansa (1):
flex: fix build with gcc-15 on host
Matthias Schiffer (1):
curl: only set CA bundle in target build
Peter Marko (1):
expat: patch CVE-2025-59375
Rasmus Villemoes (1):
iptables: remove /etc/ethertypes
Soumya Sambu (2):
elfutils: Fix CVE-2025-1376
elfutils: Fix CVE-2025-1377
.../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 ++ meta/recipes-core/expat/expat_2.6.4.bb | 25 + .../elfutils/elfutils_0.191.bb | 2 + .../elfutils/files/CVE-2025-1376.patch | 58 ++ .../elfutils/files/CVE-2025-1377.patch | 69 +++ ...01-Match-malloc-signature-to-its-use.patch | 25 + meta/recipes-devtools/flex/flex_2.6.4.bb | 1 + .../iptables/iptables_1.8.10.bb | 2 + meta/recipes-extended/pam/libpam_1.5.3.bb | 2 + ...s-chain-up-to-parent-decide_allocati.patch | 87 +++ .../gstreamer1.0-plugins-bad_1.22.12.bb | 1 + meta/recipes-support/curl/curl_8.7.1.bb | 4 +- 36 files changed, 3108 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-00.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-01.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-02.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-03.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-04.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-05.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-06.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-07.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-08.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-09.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-10.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-11.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-12.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-13.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-14.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-15.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-16.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-17.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-18.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-19.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-20.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-21.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-22.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-23.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-24.patch create mode 100644 meta/recipes-devtools/elfutils/files/CVE-2025-1376.patch create mode 100644 meta/recipes-devtools/elfutils/files/CVE-2025-1377.patch create mode 100644 meta/recipes-devtools/flex/flex/0001-Match-malloc-signature-to-its-use.patch create mode 100644 meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0005-v4l2codecs-Always-chain-up-to-parent-decide_allocati.patch
Signature · 1 line
2.43.0
PATCH 1/8 libpam: mark CVE-2025-6018 as not applicable
From: Anders Heimer <[email protected]>
CVE-2025-6018 is a local privilege escalation in PAM that requires user_readenv=1 to be enabled in the PAM configuration. The default configuration does not enable reading user environment files (user_readenv is 0 by default). Hence this vulnerability cannot be exploited using the default configuration.
--- meta/recipes-extended/pam/libpam_1.5.3.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-extended/pam/libpam_1.5.3.bb +2 -0
@@ -39,6 +39,8 @@ SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/Linux-PAM-${PV}.tar.xz \ SRC_URI[sha256sum] = "7ac4b50feee004a9fa88f1dfd2d2fa738a82896763050cd773b3c54b0a818283" +CVE_STATUS[CVE-2025-6018] = "not-applicable-config: Default PAM config does not use user_readenv=1" + DEPENDS = "bison-native flex-native libxml2-native virtual/crypt" EXTRA_OECONF = "--includedir=${includedir}/security \
Signature · 1 line
2.43.0
PATCH 2/8 expat: patch CVE-2025-59375
In reply to Steve SakomanFrom: Peter Marko <[email protected]>
Pick patch from PR mentioning this CVE [1]
It's a complex patch so I have checked diff of 2.6.4 and commit before these patches landed. There were no changes in memory allocations. Also version in scarthgap is still not that much different from current upstream master.
Ptests pass.
Also picked one documentation commit (-00) to resolve patch conflict.
Following conflicts were resolved manually:
* commit "mass-cppcheck.sh: Activate in-code suppression comments" was skipped as it only edited github actions not yet available in 2.6.4
* commit "lib: Implement tracking of dynamic memory allocations"
ale had conflict in github actions not yet available in 2.6.4
* commit "fuzz: Be robust towards NULL return from XML_ExternalEntityParserCreate" edited file "expat/fuzz/xml_lpm_fuzzer.cpp" which is not present in our version yet. Since we're not using fuzzying, this is not needed.
* the final changelog commit needed lot conflict resolution actions
Finally picked PR fixing regression [2] together with two minor commits to have a clean cherry-picks.
Also here the Changes commit needed conflict resolution.
[1] https://github.com/libexpat/libexpat/pull/1034
[2] https://github.com/libexpat/libexpat/pull/1048
--- .../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 ++ meta/recipes-core/expat/expat_2.6.4.bb | 25 + 26 files changed, 2858 insertions(+) create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-00.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-01.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-02.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-03.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-04.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-05.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-06.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-07.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-08.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-09.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-10.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-11.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-12.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-13.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-14.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-15.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-16.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-17.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-18.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-19.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-20.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-21.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-22.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-23.patch create mode 100644 meta/recipes-core/expat/expat/CVE-2025-59375-24.patch
meta/recipes-core/expat/expat/CVE-2025-59375-00.patch new file +52 -0
@@ -0,0 +1,52 @@ +From 87321ac84a0d6cb42ee64a591adc79c1ec37fb5b Mon Sep 17 00:00:00 2001 +From: Sebastian Pipping <[email protected]> +Date: Tue, 2 Sep 2025 20:52:29 +0200 +Subject: [PATCH] xmlwf: Mention supported environment variables in --help + output + +CVE: CVE-2025-59375 +Upstream-Status: Backport [https://github.com/libexpat/libexpat/commit/87321ac84a0d6cb42ee64a591adc79c1ec37fb5b] +Signed-off-by: Peter Marko <[email protected]> +--- + xmlwf/xmlwf.c | 8 ++++++++ + xmlwf/xmlwf_helpgen.py | 8 ++++++++ + 2 files changed, 16 insertions(+) + +diff --git a/xmlwf/xmlwf.c b/xmlwf/xmlwf.c +index ec7e51c9..8cfc73ca 100644 +--- a/xmlwf/xmlwf.c ++++ b/xmlwf/xmlwf.c +@@ -926,6 +926,14 @@ usage(const XML_Char *prog, int rc) { + T(" -h, --help show this [h]elp message and exit\n") + T(" -v, --version show program's [v]ersion number and exit\n") + T("\n") ++ T("environment variables:\n") ++ T(" EXPAT_ACCOUNTING_DEBUG=(0|1|2|3)\n") ++ T(" Control verbosity of accounting debugging (default: 0)\n") ++ T(" EXPAT_ENTITY_DEBUG=(0|1)\n") ++ T(" Control verbosity of entity debugging (default: 0)\n") ++ T(" EXPAT_ENTROPY_DEBUG=(0|1)\n") ++ T(" Control verbosity of entropy debugging (default: 0)\n") ++ T("\n") + T("exit status:\n") + T(" 0 the input files are well-formed and the output (if requested) was written successfully\n") + T(" 1 could not allocate data structures, signals a serious problem with execution environment\n") +diff --git a/xmlwf/xmlwf_helpgen.py b/xmlwf/xmlwf_helpgen.py +index c3257f0e..39a3dc13 100755 +--- a/xmlwf/xmlwf_helpgen.py ++++ b/xmlwf/xmlwf_helpgen.py +@@ -32,6 +32,14 @@ + import argparse + + epilog = """ ++environment variables: ++ EXPAT_ACCOUNTING_DEBUG=(0|1|2|3) ++ Control verbosity of accounting debugging (default: 0) ++ EXPAT_ENTITY_DEBUG=(0|1) ++ Control verbosity of entity debugging (default: 0) ++ EXPAT_ENTROPY_DEBUG=(0|1) ++ Control verbosity of entropy debugging (default: 0) ++ + exit status: + 0 the input files are well-formed and the output (if requested) was written successfully + 1 could not allocate data structures, signals a serious problem with execution environment
meta/recipes-core/expat/expat/CVE-2025-59375-01.patch new file +48 -0
48 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-02.patch new file +109 -0
109 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-03.patch new file +127 -0
127 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-04.patch new file +62 -0
62 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-05.patch new file +64 -0
64 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-06.patch new file +68 -0
68 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-07.patch new file +52 -0
52 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-08.patch new file +577 -0
577 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-09.patch new file +43 -0
43 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-10.patch new file +54 -0
54 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-11.patch new file +66 -0
66 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-12.patch new file +58 -0
58 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-13.patch new file +309 -0
309 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-14.patch new file +122 -0
122 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-15.patch new file +70 -0
70 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-16.patch new file +146 -0
146 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-17.patch new file +28 -0
@@ -0,0 +1,28 @@ +From a6a2a49367f03f5d8a73c9027b45b59953ca27d8 Mon Sep 17 00:00:00 2001 +From: Sebastian Pipping <[email protected]> +Date: Wed, 10 Sep 2025 19:52:39 +0200 +Subject: [PATCH] docs: Promote the contract to call XML_FreeContentModel + +.. when registering a custom element declaration handler +(via a call to function XML_SetElementDeclHandler) + +CVE: CVE-2025-59375 +Upstream-Status: Backport [https://github.com/libexpat/libexpat/commit/a6a2a49367f03f5d8a73c9027b45b59953ca27d8] +Signed-off-by: Peter Marko <[email protected]> +--- + doc/reference.html | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/doc/reference.html b/doc/reference.html +index 81da4e6c..564fc1b2 100644 +--- a/doc/reference.html ++++ b/doc/reference.html +@@ -1902,7 +1902,7 @@ struct XML_cp { + <p>Sets a handler for element declarations in a DTD. The handler gets + called with the name of the element in the declaration and a pointer + to a structure that contains the element model. It's the user code's +-responsibility to free model when finished with it. See <code> ++responsibility to free model when finished with via a call to <code> + <a href="#XML_FreeContentModel">XML_FreeContentModel</a></code>. + There is no need to free the model from the handler, it can be kept + around and freed at a later stage.</p>
meta/recipes-core/expat/expat/CVE-2025-59375-18.patch new file +74 -0
74 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-19.patch new file +103 -0
103 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-20.patch new file +285 -0
285 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-21.patch new file +196 -0
196 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-22.patch new file +37 -0
@@ -0,0 +1,37 @@ +From 5cc0010ad93868ec03248e4ac814272bc7d607bc Mon Sep 17 00:00:00 2001 +From: Sebastian Pipping <[email protected]> +Date: Fri, 19 Sep 2025 22:50:54 +0200 +Subject: [PATCH] tests: Fix test guard for test related to allocation tracking + +CVE: CVE-2025-59375 +Upstream-Status: Backport [https://github.com/libexpat/libexpat/commit/5cc0010ad93868ec03248e4ac814272bc7d607bc] +Signed-off-by: Peter Marko <[email protected]> +--- + tests/alloc_tests.c | 14 ++++++-------- + 1 file changed, 6 insertions(+), 8 deletions(-) + +diff --git a/tests/alloc_tests.c b/tests/alloc_tests.c +index dabdf0da..045447b0 100644 +--- a/tests/alloc_tests.c ++++ b/tests/alloc_tests.c +@@ -2362,14 +2362,12 @@ make_alloc_test_case(Suite *s) { + tcase_add_test__ifdef_xml_dtd( + tc_alloc, test_alloc_reset_after_external_entity_parser_create_fail); + +- tcase_add_test__ifdef_xml_dtd(tc_alloc, test_alloc_tracker_size_recorded); +- tcase_add_test__ifdef_xml_dtd(tc_alloc, +- test_alloc_tracker_maximum_amplification); +- tcase_add_test__ifdef_xml_dtd(tc_alloc, test_alloc_tracker_threshold); +- tcase_add_test__ifdef_xml_dtd(tc_alloc, +- test_alloc_tracker_getbuffer_unlimited); +- tcase_add_test__ifdef_xml_dtd(tc_alloc, test_alloc_tracker_api); ++ tcase_add_test__if_xml_ge(tc_alloc, test_alloc_tracker_size_recorded); ++ tcase_add_test__if_xml_ge(tc_alloc, test_alloc_tracker_maximum_amplification); ++ tcase_add_test__if_xml_ge(tc_alloc, test_alloc_tracker_threshold); ++ tcase_add_test__if_xml_ge(tc_alloc, test_alloc_tracker_getbuffer_unlimited); ++ tcase_add_test__if_xml_ge(tc_alloc, test_alloc_tracker_api); + + tcase_add_test(tc_alloc, test_mem_api_cycle); +- tcase_add_test__ifdef_xml_dtd(tc_alloc, test_mem_api_unlimited); ++ tcase_add_test__if_xml_ge(tc_alloc, test_mem_api_unlimited); + }
meta/recipes-core/expat/expat/CVE-2025-59375-23.patch new file +47 -0
47 lines not on this page · raw message
meta/recipes-core/expat/expat/CVE-2025-59375-24.patch new file +36 -0
@@ -0,0 +1,36 @@ +From 6fe5df59a1229ca647d365a0e3a7e17fee4d4548 Mon Sep 17 00:00:00 2001 +From: Sebastian Pipping <[email protected]> +Date: Fri, 19 Sep 2025 23:49:18 +0200 +Subject: [PATCH] Changes: Document pull request #1047 + +CVE: CVE-2025-59375 +Upstream-Status: Backport [https://github.com/libexpat/libexpat/commit/6fe5df59a1229ca647d365a0e3a7e17fee4d4548] +Signed-off-by: Peter Marko <[email protected]> +--- + Changes | 5 +++++ + 1 file changed, 5 insertions(+) + +diff --git a/Changes b/Changes +index 706a4ae1..58c222d9 100644 +--- a/Changes ++++ b/Changes +@@ -61,6 +61,9 @@ Patches: + to the pull request URL could be of help. + + Bug fixes: ++ #1046 #1047 Fix alignment of internal allocations for some non-amd64 ++ architectures (e.g. sparc32); fixes up on the fix to ++ CVE-2025-59375 in release 2.7.2 from #1034 + #980 #989 Restore event pointer behavior from Expat 2.6.4 + (that the fix to CVE-2024-8176 changed in 2.7.0); + affected API functions are: +@@ -76,7 +79,9 @@ Patches: + + Special thanks to: + Berkay Eren Ürün ++ Rolf Eike Beer + and ++ Clang/GCC UndefinedBehaviorSanitizer + Perl XML::Parser + + Security fixes:
meta/recipes-core/expat/expat_2.6.4.bb +25 -0
@@ -16,6 +16,31 @@ SRC_URI = "${GITHUB_BASE_URI}/download/R_${VERSION_TAG}/expat-${PV}.tar.bz2 \ file://CVE-2024-8176-03.patch \ file://CVE-2024-8176-04.patch \ file://CVE-2024-8176-05.patch \ + file://CVE-2025-59375-00.patch \ + file://CVE-2025-59375-01.patch \ + file://CVE-2025-59375-02.patch \ + file://CVE-2025-59375-03.patch \ + file://CVE-2025-59375-04.patch \ + file://CVE-2025-59375-05.patch \ + file://CVE-2025-59375-06.patch \ + file://CVE-2025-59375-07.patch \ + file://CVE-2025-59375-08.patch \ + file://CVE-2025-59375-09.patch \ + file://CVE-2025-59375-10.patch \ + file://CVE-2025-59375-11.patch \ + file://CVE-2025-59375-12.patch \ + file://CVE-2025-59375-13.patch \ + file://CVE-2025-59375-14.patch \ + file://CVE-2025-59375-15.patch \ + file://CVE-2025-59375-16.patch \ + file://CVE-2025-59375-17.patch \ + file://CVE-2025-59375-18.patch \ + file://CVE-2025-59375-19.patch \ + file://CVE-2025-59375-20.patch \ + file://CVE-2025-59375-21.patch \ + file://CVE-2025-59375-22.patch \ + file://CVE-2025-59375-23.patch \ + file://CVE-2025-59375-24.patch \ " GITHUB_BASE_URI = "https://github.com/libexpat/libexpat/releases/"
Signature · 1 line
2.43.0
PATCH 3/8 elfutils: Fix CVE-2025-1376
In reply to Steve SakomanFrom: Soumya Sambu <[email protected]>
A vulnerability classified as problematic was found in GNU elfutils 0.192. This vulnerability affects the function elf_strptr in the library /libelf/elf_strptr.c of the component eu-strip. The manipulation leads to denial of service. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is b16f441cca0a4841050e3215a9f120a6d8aea918. It is recommended to apply a patch to fix this issue.
Reference:
https://nvd.nist.gov/vuln/detail/CVE-2025-1376
Upstream patch:
https://sourceware.org/git/?p=elfutils.git;a=commit;h=b16f441cca0a4841050e3215a9f120a6d8aea918
--- .../elfutils/elfutils_0.191.bb | 1 + .../elfutils/files/CVE-2025-1376.patch | 58 +++++++++++++++++++ 2 files changed, 59 insertions(+) create mode 100644 meta/recipes-devtools/elfutils/files/CVE-2025-1376.patch
meta/recipes-devtools/elfutils/elfutils_0.191.bb +1 -0
@@ -28,6 +28,7 @@ SRC_URI = "https://sourceware.org/elfutils/ftp/${PV}/${BP}.tar.bz2 \ file://CVE-2025-1372.patch \ file://CVE-2025-1371.patch \ file://0007-Fix-build-with-gcc-15.patch \ + file://CVE-2025-1376.patch \ " SRC_URI:append:libc-musl = " \ file://0003-musl-utils.patch \
meta/recipes-devtools/elfutils/files/CVE-2025-1376.patch new file +58 -0
58 lines not on this page · raw message
Signature · 1 line
2.43.0
PATCH 4/8 elfutils: Fix CVE-2025-1377
In reply to Steve SakomanFrom: Soumya Sambu <[email protected]>
A vulnerability, which was classified as problematic, has been found in GNU elfutils 0.192. This issue affects the function gelf_getsymshndx of the file strip.c of the component eu-strip. The manipulation leads to denial of service. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is fbf1df9ca286de3323ae541973b08449f8d03aba. It is recommended to apply a patch to fix this issue.
Reference:
https://nvd.nist.gov/vuln/detail/CVE-2025-1377
Upstream patch:
https://sourceware.org/git/?p=elfutils.git;a=fbf1df9ca286de3323ae541973b08449f8d03aba
--- .../elfutils/elfutils_0.191.bb | 1 + .../elfutils/files/CVE-2025-1377.patch | 69 +++++++++++++++++++ 2 files changed, 70 insertions(+) create mode 100644 meta/recipes-devtools/elfutils/files/CVE-2025-1377.patch
meta/recipes-devtools/elfutils/elfutils_0.191.bb +1 -0
@@ -29,6 +29,7 @@ SRC_URI = "https://sourceware.org/elfutils/ftp/${PV}/${BP}.tar.bz2 \ file://CVE-2025-1371.patch \ file://0007-Fix-build-with-gcc-15.patch \ file://CVE-2025-1376.patch \ + file://CVE-2025-1377.patch \ " SRC_URI:append:libc-musl = " \ file://0003-musl-utils.patch \
meta/recipes-devtools/elfutils/files/CVE-2025-1377.patch new file +69 -0
69 lines not on this page · raw message
Signature · 1 line
2.43.0
PATCH 5/8 flex: fix build with gcc-15 on host
In reply to Steve SakomanFrom: Martin Jansa <[email protected]>
* fixes:
http://errors.yoctoproject.org/Errors/Details/853017/
../../flex-2.6.4/src/../lib/malloc.c:6:12: warning: conflicting types for built-in function ‘malloc’; expected ‘void *(long unsigned int)’ [-Wbuiltin-declaration-mismatch]
6 | void *malloc ();
| ^~~~~~
../../flex-2.6.4/src/../lib/malloc.c:5:1: note: ‘malloc’ is declared in header ‘<stdlib.h>’
4 | #include <sys/types.h>
+++ |+#include <stdlib.h>
5 |
../../flex-2.6.4/src/../lib/malloc.c: In function ‘rpl_malloc’:
../../flex-2.6.4/src/../lib/malloc.c:16:15: error: too many arguments to function ‘malloc’; expected 0, have 1
16 | return malloc (n);
| ^~~~~~ ~
../../flex-2.6.4/src/../lib/malloc.c:6:12: note: declared here
6 | void *malloc ();
| ^~~~~~make[2]: *** [Makefile:1431: ../lib/stage1flex-malloc.o] Error 1
--- ...01-Match-malloc-signature-to-its-use.patch | 25 +++++++++++++++++++ meta/recipes-devtools/flex/flex_2.6.4.bb | 1 + 2 files changed, 26 insertions(+) create mode 100644 meta/recipes-devtools/flex/flex/0001-Match-malloc-signature-to-its-use.patch
meta/recipes-devtools/flex/flex/0001-Match-malloc-signature-to-its-use.patch new file +25 -0
@@ -0,0 +1,25 @@ +From cec508013706ef06dbac036905a90cbe075fa03d Mon Sep 17 00:00:00 2001 +From: Richard Barnes <[email protected]> +Date: Wed, 2 Oct 2024 10:35:09 -0700 +Subject: [PATCH] Match `malloc` signature to its use + +Upstream-Status: Submitted [https://github.com/westes/flex/pull/674] + +Signed-off-by: Martin Jansa <[email protected]> +--- + lib/malloc.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/lib/malloc.c b/lib/malloc.c +index 75e8ef9..701b9b3 100755 +--- a/lib/malloc.c ++++ b/lib/malloc.c +@@ -3,7 +3,7 @@ + + #include <sys/types.h> + +- void *malloc (); ++ void *malloc (size_t n); + + /* Allocate an N-byte block of memory from the heap. + If N is zero, allocate a 1-byte block. */
meta/recipes-devtools/flex/flex_2.6.4.bb +1 -0
@@ -19,6 +19,7 @@ SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/flex-${PV}.tar.gz \ file://0001-build-AC_USE_SYSTEM_EXTENSIONS-in-configure.ac.patch \ file://check-funcs.patch \ file://0001-Emit-no-line-directives-if-gen_line_dirs-is-false.patch \ + file://0001-Match-malloc-signature-to-its-use.patch \ " SRC_URI[md5sum] = "2882e3179748cc9f9c23ec593d6adc8d"
Signature · 1 line
2.43.0
PATCH 6/8 gstreamer1.0-plugins-bad: fix buffer allocation fail for v4l2codecs
In reply to Steve SakomanFrom: Daniel Semkowicz <[email protected]>
There is a bug in GStreamer 1.22 that prevents video playback when some of the v4l2codecs are paired with sinks that do not support GstVideoMeta. This is the case of the Qt 6.9 sink used by some of the Qt components.
For example, when the v4l2codecs-vp8dec decoder is paired with QMediaPlayer, video playback fails to start with the following error:
WARN videodecoder gstvideodecoder.c:4409:gst_video_decoder_negotiate_pool: Subclass failed to decide allocation ERROR videodecoder gstvideodecoder.c:4635:gst_video_decoder_allocate_output_buffer: Failed to allocate the buffer.. WARN videodecoder gstvideodecoder.c:4409:gst_video_decoder_negotiate_pool: Subclass failed to decide allocation
WARN matroskademux matroska-demux.c:6131:gst_matroska_demux_loop: error: Internal data stream error. WARN matroskademux matroska-demux.c:6131:gst_matroska_demux_loop: error: streaming stopped, reason not-negotiated (-4)
This problem is already fixed in GStreamer 1.24, so backport the fix. This fixes the buffer allocation failure for H.264, H.265, and VP8.
--- ...s-chain-up-to-parent-decide_allocati.patch | 87 +++++++++++++++++++ .../gstreamer1.0-plugins-bad_1.22.12.bb | 1 + 2 files changed, 88 insertions(+) create mode 100644 meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0005-v4l2codecs-Always-chain-up-to-parent-decide_allocati.patch
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0005-v4l2codecs-Always-chain-up-to-parent-decide_allocati.patch new file +87 -0
@@ -0,0 +1,87 @@ +From 4e96cc4df0b6807cb487368afca64e022078ed6a Mon Sep 17 00:00:00 2001 +From: James Cowgill <[email protected]> +Date: Sun, 14 May 2023 13:23:17 +0100 +Subject: [PATCH] v4l2codecs: Always chain up to parent decide_allocation + function + +The `gst_video_decoder_negotiate_pool` function expects the +`decide_allocation` function to always provide a pool and will fail to +negotiate if the pool is missing. If we return immediately (even if we +don't need to do anything special) negotiation will fail if the +downstream element does not propose a pool. + +Fix by chaining up to the default `decide_allocation` function which +adds a fallback pool if one was not already proposed. + +Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/4630> +Upstream-Status: Backport [https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/70ff80a873d8202329df1731c06f1bfed464ad2a] +Signed-off-by: Daniel Semkowicz <[email protected]> +--- + sys/v4l2codecs/gstv4l2codech264dec.c | 3 ++- + sys/v4l2codecs/gstv4l2codech265dec.c | 3 ++- + sys/v4l2codecs/gstv4l2codecvp8dec.c | 3 ++- + 3 files changed, 6 insertions(+), 3 deletions(-) + +diff --git a/sys/v4l2codecs/gstv4l2codech264dec.c b/sys/v4l2codecs/gstv4l2codech264dec.c +index 1a6b144e9b..bd9041533b 100644 +--- a/sys/v4l2codecs/gstv4l2codech264dec.c ++++ b/sys/v4l2codecs/gstv4l2codech264dec.c +@@ -417,7 +417,7 @@ gst_v4l2_codec_h264_dec_decide_allocation (GstVideoDecoder * decoder, + /* If we are streaming here, then it means there is nothing allocation + * related in the new state and allocation can be ignored */ + if (self->streaming) +- return TRUE; ++ goto no_internal_changes; + + self->has_videometa = gst_query_find_allocation_meta (query, + GST_VIDEO_META_API_TYPE, NULL); +@@ -452,6 +452,7 @@ gst_v4l2_codec_h264_dec_decide_allocation (GstVideoDecoder * decoder, + + self->src_pool = gst_v4l2_codec_pool_new (self->src_allocator, &self->vinfo); + ++no_internal_changes: + /* Our buffer pool is internal, we will let the base class create a video + * pool, and use it if we are running out of buffers or if downstream does + * not support GstVideoMeta */ +diff --git a/sys/v4l2codecs/gstv4l2codech265dec.c b/sys/v4l2codecs/gstv4l2codech265dec.c +index 8d70d05220..3f0c08d6a4 100644 +--- a/sys/v4l2codecs/gstv4l2codech265dec.c ++++ b/sys/v4l2codecs/gstv4l2codech265dec.c +@@ -446,7 +446,7 @@ gst_v4l2_codec_h265_dec_decide_allocation (GstVideoDecoder * decoder, + guint min = 0; + + if (self->streaming) +- return TRUE; ++ goto no_internal_changes; + + self->has_videometa = gst_query_find_allocation_meta (query, + GST_VIDEO_META_API_TYPE, NULL); +@@ -465,6 +465,7 @@ gst_v4l2_codec_h265_dec_decide_allocation (GstVideoDecoder * decoder, + GST_PAD_SRC, self->min_pool_size + min + 1); + self->src_pool = gst_v4l2_codec_pool_new (self->src_allocator, &self->vinfo); + ++no_internal_changes: + /* Our buffer pool is internal, we will let the base class create a video + * pool, and use it if we are running out of buffers or if downstream does + * not support GstVideoMeta */ +diff --git a/sys/v4l2codecs/gstv4l2codecvp8dec.c b/sys/v4l2codecs/gstv4l2codecvp8dec.c +index ba63a029df..bdea1fdf76 100644 +--- a/sys/v4l2codecs/gstv4l2codecvp8dec.c ++++ b/sys/v4l2codecs/gstv4l2codecvp8dec.c +@@ -284,7 +284,7 @@ gst_v4l2_codec_vp8_dec_decide_allocation (GstVideoDecoder * decoder, + guint num_bitstream; + + if (self->streaming) +- return TRUE; ++ goto no_internal_changes; + + self->has_videometa = gst_query_find_allocation_meta (query, + GST_VIDEO_META_API_TYPE, NULL); +@@ -319,6 +319,7 @@ gst_v4l2_codec_vp8_dec_decide_allocation (GstVideoDecoder * decoder, + + self->src_pool = gst_v4l2_codec_pool_new (self->src_allocator, &self->vinfo); + ++no_internal_changes: + /* Our buffer pool is internal, we will let the base class create a video + * pool, and use it if we are running out of buffers or if downstream does + * not support GstVideoMeta */
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.22.12.bb +1 -0
@@ -9,6 +9,7 @@ SRC_URI = "https://gstreamer.freedesktop.org/src/gst-plugins-bad/gst-plugins-bad file://0001-fix-maybe-uninitialized-warnings-when-compiling-with.patch \ file://0002-avoid-including-sys-poll.h-directly.patch \ file://0004-opencv-resolve-missing-opencv-data-dir-in-yocto-buil.patch \ + file://0005-v4l2codecs-Always-chain-up-to-parent-decide_allocati.patch \ file://CVE-2025-3887-1.patch \ file://CVE-2025-3887-2.patch \ "
Signature · 1 line
2.43.0
PATCH 7/8 iptables: remove /etc/ethertypes
In reply to Steve SakomanFrom: Rasmus Villemoes <[email protected]>
When building an image including iptable built with the libnftnl PACKAGECONFIG, one hits
Downloading file:.../oe-rootfs-repo/armv8a/libkmod2 * check_data_file_clashes: Package iptables wants to install file .../rootfs/etc/ethertypes
But that file is already provided by package * netbase
This used to be handled by 0003-Makefile.am-do-not-install-etc-ethertypes.patch, but that patch got removed with the 1.8.9->1.8.10 upgrade (commit 4616ada82e70).
I think the rationale for dropping the patch was wrong; the commit log talks about xtables.conf, which is indeed gone from upstream, but said patch didn't change anything about xtables.conf, it did
-dist_conf_DATA = etc/ethertypes etc/xtables.conf
+dist_conf_DATA = etc/xtables.conf
However, instead of patching iptables to not install ethertypes, and having to forward-port that patch, it is much simpler to just remove the file in this do_install:append.
--- meta/recipes-extended/iptables/iptables_1.8.10.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-extended/iptables/iptables_1.8.10.bb +2 -0
@@ -78,6 +78,8 @@ do_install:append() { ln -sf ${sbindir}/xtables-nft-multi ${D}${sbindir}/iptables ln -sf ${sbindir}/xtables-nft-multi ${D}${sbindir}/iptables-save ln -sf ${sbindir}/xtables-nft-multi ${D}${sbindir}/iptables-restore + # ethertypes is provided by the netbase package + rm -f ${D}${sysconfdir}/ethertypes fi }
Signature · 1 line
2.43.0
PATCH 8/8 curl: only set CA bundle in target build
In reply to Steve SakomanFrom: Matthias Schiffer <[email protected]>
In native/nativesdk builds, sysconfdir refers to a recipe sysroot directory, which will disappear once the workdir is cleaned up, breaking libcurl's HTTPS connections.
By simply not setting --with-ca-bundle at all in non-target builds, curl defaults to the host system's CA certificates, which is desirable anyways to allow builds in environments that require local CA certificates.
(From OE-Core rev: 4909a46e93ba774c960c3d3c277e2a669af3fea6)
--- meta/recipes-support/curl/curl_8.7.1.bb | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
meta/recipes-support/curl/curl_8.7.1.bb +3 -1
@@ -94,11 +94,13 @@ PACKAGECONFIG[zstd] = "--with-zstd,--without-zstd,zstd" EXTRA_OECONF = " \ --disable-libcurl-option \ --disable-ntlm-wb \ - --with-ca-bundle=${sysconfdir}/ssl/certs/ca-certificates.crt \ --without-libpsl \ --enable-optimize \ ${@'--without-ssl' if (bb.utils.filter('PACKAGECONFIG', 'gnutls mbedtls openssl', d) == '') else ''} \ " +EXTRA_OECONF:append:class-target = " \ + --with-ca-bundle=${sysconfdir}/ssl/certs/ca-certificates.crt \ +" fix_absolute_paths () { # cleanup buildpaths from curl-config
Signature · 1 line
2.43.0