Linux

Rocky Linux 10.3 Released: What’s New and How to Upgrade

Rocky Linux 10.3 adds GCC 16, Go 1.27, Rust 1.97, post-quantum crypto and a GA image-builder. Here is how to…

19 November 2026  ·  4 min read  ·  Anand

Rocky Linux 10.3 Released: What's New and How to Upgrade

Rocky Linux 10.3 became generally available on 16 November 2026, with fresh installation media, container images, cloud images and live images. This point release keeps the 6.12 kernel series (6.12.0-264.16.1) but brings newer compilers and language runtimes, more post-quantum cryptography, and a fully supported image-builder tool. A few old components have also been removed. If you run Rocky Linux 10 on web, database or build servers, here is what changes and how to upgrade safely.

Developer toolchains

The developer stack gets the biggest refresh in this release:

  • GCC Toolset 16 with GCC 16.2 and Binutils 2.46. It adds C++26 reflection and contracts, and the default C++ standard is now gnu++20. Older code that assumed an earlier default may need an explicit -std= flag.
  • LLVM Toolset 22.1.8, an upgrade from the LLVM 21 series.
  • Rust 1.97, which picks up upstream changes from Rust 1.93 to 1.97 and uses v0 symbol mangling.
  • Go 1.27.3, with generic methods, encoding/json/v2 and ML-DSA post-quantum signatures in crypto/mldsa.
  • GDB 17.2, which can debug x86-64 CET shadow stacks and AArch64 Guarded Control Stacks.

For monitoring, Grafana moves to 12.4.3 and PCP to 7.1.5, and the Grafana PCP plugin 6.1.0 adds NVIDIA GPU and vLLM dashboards.

Security and cryptography

Much of the work in 10.3 prepares systems for post-quantum cryptography:

  • In FIPS mode, SSH now prefers the hybrid ML-KEM key exchanges mlkem768nistp256-sha256 and mlkem1024nistp384-sha384.
  • libreswan 5.4 supports ML-KEM-768 and ML-KEM-1024 in IKEv2.
  • audit 4.2.1 can send remote logs over TLS 1.3 with post-quantum crypto or a pre-shared key, and auditctl can filter by cgroup.
  • crypto-policies has a new NO-HMAC-SHA1 subpolicy.
  • fapolicyd 2.0.1 makes decisions on multiple threads and updates its database transactionally.
  • aide ships with a ready-made aide-check.timer and supports drop-in configs in /etc/aide.d/.

The aide-check.timer makes file integrity monitoring much easier to set up on servers that need it for compliance:

sudo dnf install aide
sudo aide --init
sudo mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz
sudo systemctl enable --now aide-check.timer

Images, installer and other changes

The image-builder CLI is now generally available. Image type names are standardised (for example aws and guest-image), and blueprints can run first-boot scripts. The web console can build bootc-compatible images from local base images. Kickstart can add anchor certificates for HTTPS downloads, which helps on internal mirrors that use a private CA. Valkey also gains RDMA support.

Removals to check before upgrading

  • WEP is gone, including from wpa_supplicant. Move any WEP networks to WPA2 or WPA3 first.
  • The ZBUD allocator is removed, and ZSMALLOC becomes the default zpool allocator for compressed swap. If you tuned zswap to use zbud, review that setting.
  • Grafana no longer supports legacy alerting or AngularJS plugins. Move dashboards and alerts before you upgrade a monitoring host.
  • Some Application Streams will not receive further updates. Check the release notes for the ones you use.

Known issues

Volumes that were explicitly created with xxhash64 through dmsetup or integritysetup cannot be accessed in FIPS mode. Installs that use encrypted DNS together with a custom CA in boot options can fail to resolve hostnames; the workaround is to set the install source in Kickstart rather than with inst.repo= or inst.stage2=.

How to upgrade

Rocky Linux 10 needs an x86-64-v3 CPU on Intel and AMD, so very old hardware and some virtual CPU models cannot run it. Other supported architectures are aarch64, riscv64, ppc64le (POWER10 and later) and s390x (z15 and later). On an existing Rocky Linux 10 system, the upgrade is a normal dnf update:

cat /etc/rocky-release
sudo dnf clean all
sudo dnf -y upgrade
sudo reboot
# after reboot
cat /etc/rocky-release
uname -r

A short checklist for production servers:

  1. Take a snapshot or a tested backup first.
  2. Upgrade a staging host and run your application tests.
  3. Rebuild C++ projects and check for problems caused by the gnu++20 default.
  4. Review zswap, Grafana and any WEP-dependent settings.
  5. Roll the upgrade out to production in batches.

You cannot upgrade in place from Rocky Linux 8 or 9 to 10. Install fresh and restore your data. Other EL10 systems can switch to Rocky with migrate2rocky.

How TechProvidence can help

We manage Rocky Linux, AlmaLinux and RHEL servers, plan major-version migrations from EL8 and EL9, and set up hardening such as AIDE, fapolicyd and FIPS policies. To plan your upgrade, contact us.

Source: Rocky Linux

Running into something similar?

We look after Linux servers, control panels and virtualization for businesses every day. If an update, vulnerability or outage here affects you, we can help.