AlmaLinux 10.3 Released: Podman 6, 36 Extra Kernel CVE Fixes and ModSecurity Returns
AlmaLinux 10.3, codenamed “Mauve Lion”, is out. Built on Linux kernel 6.12 and released right after Red Hat Enterprise Linux 10.3, it adds extra kernel security fixes, moves to Podman 6 (with breaking changes), brings back the ModSecurity web application firewall and updates its development and security tooling.

Kernel and Extra Security Fixes
AlmaLinux 10.3 follows Red Hat Enterprise Linux 10.3 and uses the Linux 6.12 kernel. The most notable security point, according to the AlmaLinux developers, is that its kernel includes fixes for 36 CVEs that were not addressed in the matching RHEL 10.3 kernel when it was released.
| Group | Count | Why it was added |
|---|---|---|
| Fixed in RHEL 10.2 but missing from the RHEL 10.3 kernel | 30 | The AlmaLinux team restored them so previously fixed vulnerabilities are not reintroduced during upgrades |
| Added in response to community requests (not in RHEL) | 6 | Requested by the community |
The practical takeaway: on upgrade, AlmaLinux aims to avoid security regressions rather than simply mirroring the upstream kernel at its release snapshot.
Podman 6: Breaking Changes to Plan For
AlmaLinux 10.3 upgrades to Podman 6. For existing container hosts this is the change that deserves the most attention, because several long-standing components are gone.
| Area | What changed in Podman 6 |
|---|---|
| Container networking | CNI support removed; Netavark is the only networking backend |
| Database backend | BoltDB dropped in favor of SQLite |
| Rootless networking | pasta replaces slirp4netns |
| Control groups | cgroups v1 support removed |
| Firewall management | Relies on nftables instead of iptables |
Configuration layout. Vendor default container configuration now lives under /usr/share/containers. Your existing files in /etc/containers stay in place and keep precedence. Separate configuration directories for rootful and rootless container storage are also supported.
ModSecurity Is Back
AlmaLinux 10.3 restores the ModSecurity web application firewall. It was available in AlmaLinux 8 and 9 but absent from versions 10.0 through 10.2. The release includes ModSecurity 2.9.14 with OWASP Core Rule Set 4.22.
Development Tools
GCC Toolset 16, LLVM Toolset 22 and GDB 17.2.
Rust 1.97, Go 1.27 and Node.js 26.
GCC Toolset 16 changes its default C++ standard from GNU++17 to GNU++20. If a project needs the older standard, compile with -std=gnu++17. The system compiler’s default is not changed.
Security Package Updates
- fapolicyd 2.0. Adds parallel policy decisions and transactional updates to the policy and trust database. If you use custom rules, test them before upgrading hardened production systems.
- Keylime 7.14. Updated remote attestation tooling.
- audit 4.2. Introduces post-quantum TLS support for remote logging.
- Libreswan 5.4. Adds support for ML-KEM post-quantum key exchange.
Features Carried Over from the 10.x Series
AlmaLinux 10.3 keeps several capabilities introduced earlier in the 10.x line:
- Btrfs support
- The CRB repository enabled by default
- x86-64-v2 builds for older processors
- 32-bit userspace packages
- Extended hardware support and additional virtualization capabilities
Images and Architectures
Installation images are available for x86_64, x86_64-v2, AArch64, ppc64le and s390x. Live images and generic cloud images are also available. Additional cloud, container and Raspberry Pi images are being rolled out separately, so check the project’s download page if you need one of those. The release announcement and the 10.3 release notes are linked in the sources below.
AlmaLinux 9.9, codenamed “Chartreuse Bobcat”, was announced alongside it, following RHEL 9.9. It brings security fixes, refreshed system packages and updated development tools for users who stay on the 9.x series.
Before You Upgrade: A Practical Checklist
This checklist is general good practice for a minor-release upgrade. Always follow the official release notes first.
- Read the release notes for AlmaLinux 10.3 and note anything that touches your workloads.
- Snapshot or back up the system, and for VMs take a snapshot before updating.
- Audit your container hosts for CNI plugins, iptables-dependent rules and cgroups v1 assumptions. To see which cgroup version a host is using, run:
The outputstat -fc %T /sys/fs/cgroupcgroup2fsmeans cgroups v2. Check your Podman networking backend as well before moving to Podman 6. - Review custom ModSecurity rules against CRS 4 if you are bringing configurations over from AlmaLinux 9.
- Test fapolicyd rules on a non-production system if you run it in enforcing mode.
- Check C++ builds if you use GCC Toolset 16, since the default standard is now GNU++20.
- Roll out gradually. Update a staging host first, then a small production group, and keep a rollback path.
For more Linux and infrastructure guides, see VMoreCloud .
Frequently Asked Questions
What is the codename of AlmaLinux 10.3?
“Mauve Lion”. AlmaLinux 9.9, released alongside it, is codenamed “Chartreuse Bobcat”.
Which kernel does AlmaLinux 10.3 use?
Linux kernel 6.12, with fixes for 36 CVEs that were not addressed in the RHEL 10.3 kernel at release time.
What breaks with Podman 6?
CNI networking, the BoltDB database backend and cgroups v1 support were removed. Netavark is now the only networking backend, pasta replaces slirp4netns for rootless networking, and firewall management uses nftables instead of iptables.
Is ModSecurity available in AlmaLinux 10.3?
Yes. ModSecurity 2.9.14 with OWASP Core Rule Set 4.22 is included. It was missing from AlmaLinux 10.0 through 10.2.
Which architectures are supported?
x86_64, x86_64-v2, AArch64, ppc64le and s390x installation images are available, plus live and generic cloud images.
Sources and Further Reading
- AlmaLinux announcement: 10.3 and 9.9 stable
- AlmaLinux 10.3 release notes
- Linuxiac: AlmaLinux 10.3 Released with Podman 6, Enhanced Security
- Linuxiac: RHEL 10.3 Released with Linux Kernel 6.12, GCC 16, and Sealed Images
Details in this article are based on the AlmaLinux announcement as reported by Linuxiac. Confirm package versions and upgrade steps in the official release notes before changing production systems.

