Skip to content

Conversation

@azurelinux-security
Copy link
Contributor

@azurelinux-security azurelinux-security commented Feb 3, 2026

Auto Patch kured for CVE-2025-11065.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1042063&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?

Change Log
Does this affect the toolchain?

YES/NO

Associated issues
  • N/A
Links to CVEs
Test Methodology

@Kanishk-Bansal Kanishk-Bansal marked this pull request as ready for review February 3, 2026 12:46
@Kanishk-Bansal Kanishk-Bansal requested a review from a team as a code owner February 3, 2026 12:46
@Kanishk-Bansal
Copy link
Contributor

Changed the patching command
image

@Kanishk-Bansal
Copy link
Contributor

Buddy Build

Copy link
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Patch Analysis

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

Patch has been backported.

For file, decode_hooks.go
Many APIs are not present in the codebase. Below are the missing APIs in our version. Also, attaching the .rej file for reference.(changed the fileformat to .patch as github doesnot support .rej file to upload).
StringToURLHookFunc(), StringToNetIPAddrHookFunc(), StringToNetIPAddrPortHookFunc(), StringToNetIPPrefixHookFunc(), StringToInt8HookFunc(), StringToUint8HookFunc(), StringToInt16HookFunc(), StringToUint16HookFunc(), StringToInt32HookFunc(), StringToUint32HookFunc() StringToInt64HookFunc(), StringToUint64HookFunc(), StringToIntHookFunc(), StringToUintHookFunc(), StringToFloat32HookFunc(), StringToFloat64HookFunc(), StringToBoolHookFunc(), StringToComplex64HookFunc() StringToComplex128HookFunc()
decode_hooks.go-rej.patch

There is no decode_hooks_test.go file in our codebase.

There is noerrors.go file in our codebase but there is error.go file. So, added new APIs into this file.

For file mapstructure.go
As newDecodeError is not defined in error.go file, upstream patch failed to apply. As per the fix, err is replaced with wrapStrconvNumError(err)

@Kanishk-Bansal Kanishk-Bansal added the ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review label Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0 AutoPR-Security Packaging ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants