[AutoPR- Security] Patch gawk for CVE-2026-40553, CVE-2026-40468, CVE-2026-40467 [MEDIUM]

[azurelinux-security]

Auto Patch gawk for CVE-2026-40553, CVE-2026-40468, CVE-2026-40467.

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

CVE-2026-40553 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160402&view=results
CVE-2026-40468 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160401&view=results
CVE-2026-40467 : Single Patch Backporter Pipeline Run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1160403&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 gawk for CVE-2026-40553 (MEDIUM), CVE-2026-40468 (LOW), CVE-2026-40467 (MEDIUM).

Change Log

• CVE-2026-40553
• CVE-2026-40468
• CVE-2026-40467

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-40553
• https://nvd.nist.gov/vuln/detail/CVE-2026-40468
• https://nvd.nist.gov/vuln/detail/CVE-2026-40467

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.

[AkarshHCL]

1. Changed from applying each patch one by one to using autosetup macro.
2. Skipped the failing pma test due to reason-persistent memory allocator requires MAP_FIXED mmap which may not work reliably in chroot build environments.
   3.Tried local build after these fixes screenshot of successful build-

4. Patches are also getting applied cleanly - 5. Did changes to AI backported patches which Ai missed , to make them in sync with upstream patches.

[v-aaditya]

Peer-Review -

1. All the 3 CVEs affect the gawk package version 5.2.2 as it is in affected range of <= 5.4.0 and affected files and functions are present in current source.
2. All the 3 AI patches after modification, completely match with upstream patches respectively.
3. AI patches have respective upstream patch references.
4. Local build is successful and patches apply cleanly.
5. Re-triggered the Buddy Build.
6. LGTM. Need to look into circular dependency issue. PR can be opened for review once the Buddy Build has passed.

[Kanishk-Bansal]

/azurepipelines run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
2 pipeline(s) were filtered out due to trigger conditions.

[Kanishk-Bansal]

• CVE-2026-40467 - matches upstream
• CVE-2026-40468 - core fix matches upstream
• CVE-2026-40553 - added fix lines identical to upstream

Overall LGTM

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

[Kanishk-Bansal]

skipping is the only solution to test failures because of chroot restrictions