diff --git a/.github/workflows/build-gfx11-rocm.yml b/.github/workflows/build-gfx11-rocm.yml
index 71d7d94302c..33d6b40c8fb 100644
--- a/.github/workflows/build-gfx11-rocm.yml
+++ b/.github/workflows/build-gfx11-rocm.yml
@@ -10,24 +10,24 @@ on:
       rocm_version:
         description: 'ROCm version to use (e.g., 7.14.0a20260608) or "latest" to auto-detect'
         required: false
-        default: '7.14.0a20260608'
+        default: 'latest'
       create_release:
         description: 'Publish a dated GitHub Release (b<YYYYMMDD>) with the built binaries. Set true only for the nightly dispatch.'
         required: false
         default: 'false'
 
-# Pinned to ROCm 7.14.0a20260608: last known-good nightly (libhsa-runtime64 build
-# d34cbb6409). The 7.14.0a20260609 and newer nightlies regressed libhsa-runtime64
-# (build 1b2a555677), which segfaults in GpuAgent::InitDma on the gfx115x runners.
-# See https://github.com/ROCm/TheRock/issues/5763. Pass rocm_version=latest manually
-# to track the newest nightly.
+# Tracks the latest multiarch ROCm nightly (auto-detected). The earlier pin to
+# 7.14.0a20260608 worked around a libhsa-runtime64 regression (build 1b2a555677)
+# that segfaulted in GpuAgent::InitDma on the gfx115x runners; that issue
+# (https://github.com/ROCm/TheRock/issues/5763) is now resolved. Pass an explicit
+# rocm_version (e.g. 7.14.0a20260608) to pin a specific nightly again.
 #
 # Nightly is driven externally (GitHub cron only fires from the default branch).
 # On a host you control, with `gh` authenticated (token scope: repo + workflow):
-#   0 13 * * *  gh workflow run build-gfx11-rocm.yml --repo ROCm/llama.cpp --ref gfx11 -f rocm_version=7.14.0a20260608
+#   0 13 * * *  gh workflow run build-gfx11-rocm.yml --repo ROCm/llama.cpp --ref gfx11 -f rocm_version=latest
 
 env:
-  ROCM_VERSION: ${{ github.event.inputs.rocm_version || '7.14.0a20260608' }}
+  ROCM_VERSION: ${{ github.event.inputs.rocm_version || 'latest' }}
 
 jobs:
   build-ubuntu: