2026.9.2

Release Highlights

This recovery release supersedes the withdrawn 2026.9.1 release. It replaces the unstable CCA host stack with the coherent v17 stack previously validated on the main branch.

  • Linux moves from cca-host/v13 to immutable commit 16b5782a3f8fc9b6c796662c84fcc3af1d575157 from the v17 integration branch.

  • kvmtool uses tag cca-kvm-v20, which identifies the matching v17 integration commit.

  • TF-RMM uses immutable commit eba8e742128079135cfbce3de3256c5d326b530b.

  • KVM unit tests use the matching cca-rmm-v2.0 tag.

The v13 host implementation could free a power-of-two allocation larger than the reclaimed Realm range. Repeated Realm creation and destruction could then corrupt adjacent live pages, leading to use-after-free reports, RCU stalls, or kernel panics. The selected v17 implementation allocates and frees those ranges at their exact sizes.

CCA Realm Validation

The automated CCA test boots a Realm Linux guest and then runs every supported KVM unit-test invocation in the same retained host session. The launcher uses one vCPU, 512 MiB of memory, --no-pvtime, --force-pci, and a host-local copy of the guest disk.

RMM v2 deliberately disables Realm PMU support. The adapter explicitly skips the 11 PMU invocations and runs the other 26 upstream invocations. Unexpected kvmtool failures remain fatal.

Test Report Summary

The main-first change passed the full non-smoke GitLab pipeline on both amd64 and native arm64 runners: all ten jobs and all 616 reported tests passed. The run included the complete supported CCA Realm sequence on both architectures and showed none of the v13 corruption signatures.

Publication is additionally gated on a full non-smoke pipeline for the exact final 2026.9.2 maintenance-branch tree.