summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/elfutils
diff options
context:
space:
mode:
authorPeter Marko <peter.marko@siemens.com>2025-10-21 21:19:57 +0200
committerSteve Sakoman <steve@sakoman.com>2025-11-03 07:17:01 -0800
commit2421e79018781d1b85a577cf6f6cbd6294a712ca (patch)
tree3abf7b4b3c90f532413ab44f0749aa6efae1f9f7 /meta/recipes-devtools/elfutils
parent251d8b676e98fee2b2a9dc0dda2caede9f5acb19 (diff)
downloadpoky-2421e79018781d1b85a577cf6f6cbd6294a712ca.tar.gz
expat: patch CVE-2025-59375
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 (From OE-Core rev: 684d3cdbc08ce41dc1f92e1f228eee34bc2bc1fe) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'meta/recipes-devtools/elfutils')
0 files changed, 0 insertions, 0 deletions