[AUTO-CHERRYPICK] Fix : patch application of CVE-2025-4802 in glibc (re-apply: #14582) - branch 3.0-dev

[aaruag]

This is an auto-generated pull request to cherry-pick commit d3975f8 to 3.0-dev. Original PR: #14669

[CBL-Mariner-Bot]

🚨 PR Check Failed - Critical Issues Found

Found 2 critical/error issue(s) that must be fixed.

🔍 Critical Issues Detected:

1. Missing Patch File (ERROR)
   • Patch file 'CVE-2022-2990.patch' is referenced in the spec but not found in the directory
   • 💡 Fix: Add the missing patch file or update the Patch reference
2. Missing Patch File (ERROR)
   • Patch file 'CVE-2022-2989.patch' is referenced in the spec but not found in the directory
   • 💡 Fix: Add the missing patch file or update the Patch reference

🤖 AI Analysis Summary:

Brief Analysis: The spec file is in a conflicted merge state showing two divergent histories – one branch uses version 1.41.4 with a “0001-Run-selective-tests.patch” while the other branch (commit d3975f8) switches to version 1.18.0 and references a CVE patch (“CVE-2022-2990.patch”). This discrepancy creates inconsistency in versioning and patch application.

Critical Issues Found:
• Merge conflict markers remain in the spec file.
• The CVE-2022-2990.patch reference is declared but the file is missing.
• Version numbers and changelog entries are inconsistent.

Recommended Actions:
• Resolve the merge conflict and choose one consistent version and patch set.
• Either provide the missing CVE-2022-2990.patch file or update the spec to keep the correct, available patch.
• Update the changelog to clearly document any CVE fix with proper CVE IDs and ensure all patch references use sequential numbering and proper %patch/%autopatch directives.

---

📋 For detailed analysis and recommendations, check the Azure DevOps pipeline logs.