[AutoPR- Security] Patch perl for CVE-2026-57433 [CRITICAL]

[azurelinux-security]

Auto Patch perl for CVE-2026-57433.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1161391&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 perl for CVE-2026-57433 (CRITICAL).

Change Log

• CVE-2026-57433

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-57433

Test Methodology

• Pipeline build id: Buddy Build URL

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[v-aaditya]

CVE-2026-57433 -

1. The CVE affects the Storable package in perl with version 3.31 which is in affected range of < 3.41.
2. The affected file dist/Storable/Storable.xs is present and the affected function and code is also present.
3. The AI patch has been modified to add upstream patch reference and to update the version information.
4. The AI patch matches with upstream patch completely.
5. The AI patch has an upstream patch reference.
6. The local build is successful and patch applies cleanly.
7. The Buddy Build has been re-triggered and it has passed.

[Kanishk-Bansal]

core logic matches upstream, with correct backporting to the 5.38.2 base. The security fix in dist/Storable/Storable.xs (retrieve_hook_common) is byte-identical to upstream: it adds a guard rejecting len3 == I32_MAX (CROAK("Invalid count of hook data items")) before av_extend(av, len3 + 1), preventing the signed-int overflow when unpacking a hook-data-item list.

[Kanishk-Bansal]

• Buddy Build 
• patch applied during the build (check rpm.log)
• patch include an upstream reference
• PR has security tag