Daily Tech Now

Daily News on AI, Big Tech, Linux, Security & Gadgets

AlmaLinux 10.3 and 9.9 Add Kernel Fixes RHEL Lacks, but the NoisyTCP Patch Is Still in Testing

AlmaLinux 10.3 and 9.9 shipped on November 16 with kernels that fix dozens of CVEs still open in the matching Red Hat Enterprise Linux kernels. On the same day, the project also disclosed NoisyTCP, a bug that lets a remote attacker crash a Linux server. That fix is not in the new release kernels. It…

AlmaLinux 10.3 release with extra kernel security fixes and AlmaLinux 9.9 upgrade checklist

AlmaLinux 10.3 and 9.9 shipped on November 16 with kernels that fix dozens of CVEs still open in the matching Red Hat Enterprise Linux kernels. On the same day, the project also disclosed NoisyTCP, a bug that lets a remote attacker crash a Linux server. That fix is not in the new release kernels. It sits in the AlmaLinux testing repository for now.

The AlmaLinux OS Foundation release announcement calls the new versions “Mauve Lion” (10.3) and “Chartreuse Bobcat” (9.9). They follow RHEL 10.3 and RHEL 9.9. This guide covers what changes for admins, what to check before upgrading, and how to deal with NoisyTCP.

AlmaLinux 10.3 and 9.9 at a glance

Item AlmaLinux 10.3 AlmaLinux 9.9
Codename Mauve Lion Chartreuse Bobcat
Release kernel 6.12.0-264.16.1.el10_3 5.14.0-741.22.1.el9_9
ISO architectures x86_64, x86_64_v2, aarch64, ppc64le, s390x x86_64, aarch64, ppc64le, s390x
Kernel CVE fixes not in the matching RHEL kernel 36 (30 restored, 6 community requests) 44 (43 restored, 1 community request)
NoisyTCP-patched kernel (testing repo) 6.12.0-264.16.2.el10_3 5.14.0-741.22.2.el9_9
New toolchains and runtimes GCC Toolset 16, LLVM Toolset 22, Rust 1.97, Go 1.27, GDB 17.2, Node.js 26 GCC Toolset 16 (Toolset 15 kept), LLVM Toolset 22, Rust 1.97, Go 1.27, GDB 17.2, PHP 8.4 and Node.js 26 module streams

Why the extra kernel fixes matter

AlmaLinux compared the new RHEL kernels with the last RHEL 9.8 and RHEL 10.2 kernels. The older kernels carried fixes that the new ones do not. The gap covers 43 CVEs on the 9 line and 30 on the 10 line.

The announcement says the team does not know why those fixes were left out. It did not want an update to bring old vulnerabilities back, so it added the fixes to both AlmaLinux kernels. In plain terms, a system moving from 9.8 to RHEL 9.9 could lose protection it already had. AlmaLinux users avoid that step back.

Community requests add more patches: one CVE on 9.9 and six on 10.3. One of them is CVE-2026-98276 (CVSS 7.0), where the kernel function sock_gettstamp() runs without the socket lock. The release notes say RHEL has never fixed it.

Examples from the release notes

The AlmaLinux 9.9 release notes list each restored CVE with its score. Examples include CVE-2026-53360 (CVSS 8.8), a KVM SEV issue, and CVE-2026-68156 (CVSS 8.8) in libceph. Scores in the restored 9.9 set range from 3.3 to 8.8.

The AlmaLinux 10.3 release notes also list CVE-2026-53360. They add CVE-2026-80792 (CVSS 7.0), a use-after-free bug in the IPv6 code.

AlmaLinux 9.9 keeps one more kernel change from 9.8. It is a backport of upstream commit d919a1e79bac. The patch stops systemd and ps from using too much CPU during task cleanup. The AlmaLinux Engineering Steering Committee (ALESCo) approved it, and RHEL 9.9 does not include it.

Both releases also bundle fixes AlmaLinux shipped earlier as separate updates. These cover PwnEscape (CVE-2026-99999), php2shell (CVE-2026-109618 and CVE-2026-109619), ZDI-CAN-33367 and CVE-2026-98432.

NoisyTCP: what it is and how to patch now

NoisyTCP (CVE-2026-99288) is a race condition in the Linux kernel’s TCP code. According to AlmaLinux’s NoisyTCP advisory, an attacker needs no account. Sending TCP packets to a listening port is enough to make the kernel panic. Red Hat rates the bug Important and says it affects availability, not data integrity or code execution.

The bug dates back to Linux 4.4 in 2015. AlmaLinux 8, 9 and 10 are affected, and Red Hat lists RHEL 8, 9 and 10 as affected too. AlmaLinux reported no known attacks in the wild when it published the advisory.

The race needs packets handled on more than one CPU. That means a network card with two or more receive queues, or RPS turned on. The researcher reports crashes on virtual machines within 5 seconds to 2 minutes. A quiet bare-metal server took about 14 hours.

The researcher also describes a harder-to-trigger variant that leads to a use-after-free. Hyunwoo Kim found the bug and wrote the upstream fix, commit 4e2b3ef19e0e. The disclosure went to the oss-security list on November 15.

Steps to install the patched kernel

AlmaLinux shipped patched kernels before CentOS Stream and RHEL, with ALESCo approval. Its advisory said no fixed RHEL kernel existed yet. The patched builds are:

  • AlmaLinux 8: kernel-4.18.0-553.186.2.el8_10
  • AlmaLinux 9: kernel-5.14.0-741.22.2.el9_9
  • AlmaLinux 10: kernel-6.12.0-264.16.2.el10_3

To install one from the testing repository, run:

sudo dnf install -y almalinux-release-testing
sudo dnf update 'kernel*' --enablerepo=almalinux-testing
sudo reboot

After the reboot, check the version with uname -r or rpm -q kernel. On production machines, turn the testing repo off again with sudo dnf config-manager --disable almalinux-testing. AlmaLinux asks for extra testing on version 8, because its older kernel needed an adapted fix.

Temporary workarounds

AlmaLinux lists two stopgaps. Neither replaces the patch.

  • Turn off SYN cookies with sudo sysctl -w net.ipv4.tcp_syncookies=0. This closes the crash path but removes SYN flood protection. Containers with their own network namespace need the same setting. It does not cover the second variant.
  • Use one receive queue and disable RPS and RFS. This removes the multi-CPU race but cuts network throughput. The settings do not survive a reboot, and some network cards do not allow queue changes.

What changes for you before upgrading

The 9.9 release notes say an AlmaLinux 9 system upgrades with dnf upgrade -y. A few changes in both releases can break working setups, so test them first.

Changes in both 10.3 and 9.9

  • authselect no longer merges groups by default. If you combine group sources, such as local files and SSSD, run authselect enable-feature with-group-merging.
  • fapolicyd jumps from 1.4 to 2.0, with parallel decisions and transactional database updates. AlmaLinux advises testing rules on a non-production host.
  • GCC Toolset 16 defaults to gnu++20 instead of gnu++17. Add -std=gnu++17 if your code needs the old standard. The system compiler does not change.

AlmaLinux 10.3 only

ModSecurity returns to AlmaLinux 10 as version 2.9.14, with the OWASP Core Rule Set (CRS) 4.22. It was missing from 10.0 through 10.2. AlmaLinux 9 ships ModSecurity 2.9.6 with CRS 3.3. CRS 4 reorganized its rules, so anyone moving a web firewall setup from 9 to 10 should review custom rules.

Podman 6 brings bigger changes for container hosts:

  • Vendor defaults move from /etc/containers to /usr/share/containers. Local settings in /etc/containers still win.
  • Netavark is now the only network backend, as CNI is gone.
  • SQLite replaces BoltDB, and pasta replaces slirp4netns.
  • cgroups v1 support is removed, and nftables replaces iptables.
  • Rootful and rootless storage get separate drop-in directories.

Security tools also move up: fapolicyd 2.0, Keylime 7.14, audit 4.2 with post-quantum TLS for remote logging, and libreswan 5.4 with ML-KEM key exchange.

AlmaLinux 9.9 only

Version 9.9 adds PHP 8.4 and Node.js 26 module streams. The release notes also list .NET 11 as a new package. opencryptoki 3.27 adds ML-DSA and ML-KEM key types.

How AlmaLinux 10.3 still differs from RHEL 10.3

Most of these differences carry over from earlier 10.x releases. They are not new in 10.3.

  • Btrfs support, including booting from a Btrfs volume.
  • x86_64_v2 builds for older processors, with matching EPEL coverage.
  • i686 packages for 32-bit software and CI jobs. This is userspace only, with no 32-bit installer or kernel. Packages live on vault.almalinux.org, and containers run with docker run --platform linux/386. Support arrived in 10.2 and is planned through 2035.
  • CRB enabled by default, plus frame pointers, SPICE and KVM on IBM POWER.
  • Older hardware support: restored device IDs in the aacraid, be2iscsi, be2net, hpsa, lpfc, megaraid_sas, mlx4_core, mpt3sas, mptsas, qla2xxx and qla4xxx drivers. These cover cards from HP, LSI, Adaptec, Dell PERC, QLogic, Emulex and Mellanox.

AlmaLinux removes Red Hat-specific packages such as redhat-release, insights-client and virt-who. The 9.9 notes add that Windows SPICE and virtio-win packages are not included either.

Download options and images

Each version offers three ISOs: a network boot image, a minimal image for offline installs and a full DVD image. Torrents are available too. Live Media, Generic Cloud and OpenNebula images went out at launch, with Raspberry Pi images to follow.

The announcement also lists container, LXC/LXD, WSL and Vagrant images, plus cloud images for AWS, Azure, Google Cloud and Oracle Cloud. Vagrant boxes now come from AlmaLinux’s own catalog.

The two official sources differ on live desktops. The announcement lists GNOME, GNOME-mini, KDE, XFCE and MATE across its live media. The AlmaLinux Live Media wiki page, last updated in June 2026, lists only GNOME and KDE for AlmaLinux 10.

What remains unclear

AlmaLinux has not said when the NoisyTCP kernels will leave testing. Until they do, a fresh 10.3 or 9.9 install runs a kernel without that fix. The sources also contain no explanation from Red Hat for the fixes missing from its new kernels.

Admins who run internet-facing servers should watch the AlmaLinux blog for the stable kernel push. Bug reports go to bugs.almalinux.org or the AlmaLinux chat.

About the Author

Trang Nguyen Avatar

Leave a Reply

Your email address will not be published. Required fields are marked *