[AutoPR- Security] Patch moby-engine for CVE-2025-58183 [MEDIUM]

[azurelinux-security]

Auto Patch moby-engine for CVE-2025-58183.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=983215&view=results

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?

• Auto Patch moby-engine for CVE-2025-58183 (MEDIUM).

Change Log

• CVE-2025-58183

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-58183

Test Methodology

• Pipeline build id: Buddy Build URL

[xordux]

• Patch applied in logs: Yes
• Upstream Patch matches: Yes, backport seems correct.
• Test failure: No

[0xba1a]

• Patch applied in logs: Yes
• Upstream Patch matches: Yes, backport seems correct.
• Test failure: No

@xordux Please check whether the patch fixes the problem logically and not introducing any possible regression and provide signoff.

[kgodara912]

We will verify CVE applicability once. --> As per this, #15098 (review), removing "Request changes". Will leave for above comment to be resolved.

[xordux]

I signoff this patch. It fixes the problem logically and not introducing any possible regression.

One point that might cause confusion is: “Why doesn’t this CVE patch include the maxSpecialFileSize value?”
The reason is that maxSpecialFileSize is already set by another patch in moby-engine, which you can find here: link to patch

[kgodara912]

Patch matches with upstream reference except test files. Buddy build is successful. LGTM.