[HIGH] Patch coredns for CVE-2025-47950

[aninda-al]

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

Address CVE-2025-47950

Upstream Patch Reference: coredns/coredns@efaed02
Upstream patch applies cleanly?
NO
hunk Failed for 4 of the 10 files.

List of files unavailable/skipped during backporting

• None: All 10 files listed in the upstream patch were included during patch creation.

Note: There is an existing test failure for this package and I verified that it was not introduced during this CVE fix.

Change Log

• modified: SPECS/coredns/coredns.spec
• modified: SPECS/coredns/CVE-2025-47950.patch

Does this affect the toolchain?

NO

Associated issues

• #NA

Links to CVEs

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

Test Methodology

• Pipeline build id: local build
• Patch applies cleanly during package build?
  YES
  

[Kanishk-Bansal]

/azurepipelines run

[Kanishk-Bansal]

refactor prep to
%autosetup -p1 -a1

[aninda-al]

refactor prep to %autosetup -p1 -a1

I did refactor the prep section, but I had to swap p & a to be consistent with the current steps

[Kanishk-Bansal]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jslobodzian]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).