libsoup: add patches for CVE-2024-52530, CVE-2024-52531, CVE-2024-52532

[trungams]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?
Add patches for CVE-2024-52530, CVE-2024-52531, CVE-2024-52532 affecting libsoup

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2024-52530
• https://nvd.nist.gov/vuln/detail/CVE-2024-52531
• https://nvd.nist.gov/vuln/detail/CVE-2024-52532

[mbykhovtsev-ms]

It seems some of the patches are not applying cleanly. You might need to tweak them

[trungams]

@mbykhovtsev-ms The patches are fine, it's the patch command (%autosetup) that was missing -p1 flag initially so it could not apply. The most recent pipeline run was cancelled for some reason. Should I rerun it?

[mbykhovtsev-ms]

@mbykhovtsev-ms The patches are fine, it's the patch command (%autosetup) that was missing -p1 flag initially so it could not apply. The most recent pipeline run was cancelled for some reason. Should I rerun it?

Ah, that make sense. Yes, we need to re-run it to verify it does not break any other packages that depend on this. I restarted it