Skip to content

[AutoPR- Security] Patch tensorflow for CVE-2026-2492 [MEDIUM]#15963

Open
azurelinux-security wants to merge 2 commits intomicrosoft:mainfrom
azurelinux-security:azure-autosec/tensorflow/2.0/1055918
Open

[AutoPR- Security] Patch tensorflow for CVE-2026-2492 [MEDIUM]#15963
azurelinux-security wants to merge 2 commits intomicrosoft:mainfrom
azurelinux-security:azure-autosec/tensorflow/2.0/1055918

Conversation

@azurelinux-security
Copy link
Copy Markdown
Contributor

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

Auto Patch tensorflow for CVE-2026-2492.

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

Buddy Build

@akhila-guruju
Copy link
Copy Markdown
Contributor

akhila-guruju commented Mar 9, 2026

Root cause: The build restores cached Bazel state (%{SOURCE1} into /root), and that can include stale/partial Bazel install artifacts. Bazel validates those files at startup; if any jar is missing/changed, it hard-fails before the actual build.
Screenshot 2026-03-09 105228

Fix: rm -rf /root/.cache/bazel/_bazel_root/install. This forces Bazel to regenerate a clean install cache for the current build invocation.

@akhila-guruju
Copy link
Copy Markdown
Contributor

akhila-guruju commented Mar 9, 2026

Buddy Build after recent commit.
Build has passed. ARM installation test failed because, the package is only for x86_64 ExclusiveArch: x86_64
Patch looks good w.r.t upstream patch.

@Kanishk-Bansal Kanishk-Bansal marked this pull request as ready for review March 9, 2026 08:28
@Kanishk-Bansal Kanishk-Bansal requested a review from a team as a code owner March 9, 2026 08:28
@Kanishk-Bansal
Copy link
Copy Markdown
Contributor

Patch Analysis ( patch matches upstream)

  • Buddy Build (Build has passed. ARM installation test failed because, the package is only for x86_64 ExclusiveArch: x86_64.)
  • patch applied during the build (check rpm.log)
  • patch include an upstream reference
  • PR has security tag

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants