
Checklist para proteger Linux (desktop e VPS) da CVE-2026-98432
Status as of November 2, 2026. This flaw is changing fast. Before following any steps, check your distribution's tracker (links in step 1).
There is a flaw in the Linux kernel's TCP/IPv4 code (a use-after-free in the handshake) that can be exploited over the network, without a password and without any user action. The kernel CVE team gave it a CVSS 9.8 (critical) score. The complete fix is to run a kernel patched by your vendor: in general this means updating and rebooting. Some vendors also offer live patching. Until the fix is available, you can greatly reduce your exposure.
go.mod declares go 1.24 or newer and the kernel allows MPTCP.The real risk depends on the case. The Go team warns that the bug does not depend on MPTCP and that systems without an MPTCP listener can also be vulnerable. As of November 1 there had been no public report of active exploitation, but repositories already existed on GitHub claiming to have code that triggers the race.
grep -E '^(PRETTY_NAME|VERSION_ID)=' /etc/os-release
uname -r # kernel que está rodando AGORA
uname -v # no Debian mostra a versão do pacote em execução
systemd-detect-virt # tipo de virtualização (none, kvm, lxc, openvz, wsl...)
Run on the host, never inside a container. Before updating, find out who provides the kernel that is running:
systemd-detect-virt shows | Who updates the kernel |
|---|---|
none, kvm, qemu, vmware, microsoft, xen, amazon | You, through your distribution (steps 1 and 2) |
lxc, openvz (container-based VPS) | The provider. Updating packages inside the VPS does not change the kernel. Ask support whether the host has already been patched |
wsl (WSL2 on Windows) | Microsoft. Update through Windows with wsl --update and check the status on Microsoft's channels |
Cloud images and appliances that ship their own kernel depend on the image vendor.
Each distribution applies the fix under its own version number. Compare within the same distribution version and the same kernel variant (generic, -aws, -azure, -lowlatency, HWE, real-time). Variants have their own numbers: check your line in the tracker.
| Distribution | Status as of 02/11/2026 | Version with fix | Tracker |
|---|---|---|---|
| Ubuntu 16.04 to 26.10 | ❌ No fix published ("work in progress") | 24.04 generic: expected in 6.8.0-149. 22.04 generic: expected in 5.15.0-203 | ubuntu.com |
| Debian 13 trixie | ✅ Fixed | source package linux 6.12.113-1 (DSA-6568-1) | security-tracker |
| Debian 12 bookworm | ✅ Fixed | source package linux 6.1.190-1 (DLA-4841-1) or linux-6.12 6.12.113-1~deb12u1 (DLA-4850-1) | security-tracker |
| RHEL 8 / 9 / 10 | ✅ Fixed on 01/11 | kernel-4.18.0-553.182.1.el8_10 / kernel-5.14.0-687.64.1.el9_8 / kernel-6.12.0-211.72.1.el10_2 | Red Hat |
| AlmaLinux 8 / 9 / 10 | ✅ Fixed (production on 02/11) | Same versions as RHEL above | AlmaLinux |
| Oracle Linux (UEK kernel) | ✅ Fixed on 16/10 | See advisories ELSA-2026-500397, 500398 and 500399 | Oracle |
| Amazon Linux 2 and 2023 | ✅ Fixed | See ALAS2023-2026-3365 (default AL2023 kernel) and ALAS2-2026-4065 (AL2) | ALAS |
| SUSE / openSUSE | 🟡 Partial: SLES 16.0, SLES 15 SP4 to SP6 LTSS and Leap 16.0 fixed. SLES 15 SP7: kernel still in progress, live patch already released | SLES 16.0 / Leap 16.0: kernel-default 6.12.0-160000.40.1 | SUSE |
| Kernel compiled by you | ✅ Fixed in stable versions | 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, 7.3 (each applies to its own line) | fix commit |
For Oracle and Amazon, the advisory lists the fixed package for each kernel variant. Use that number for comparison.
For distributions not in the table (Fedora, Arch, Rocky, Pop!_OS and others), check their security tracker. Linux Mint uses the Ubuntu kernel and follows Ubuntu's status.
Check whether a kernel update is already available:
# Debian / Ubuntu / Mint
sudo apt update && apt list --upgradable 2>/dev/null | grep -E '^linux-'
# RHEL / AlmaLinux / Rocky / Oracle / Fedora / Amazon Linux 2023
sudo dnf check-update 'kernel*'
# Amazon Linux 2
sudo yum check-update 'kernel*'
# openSUSE / SLES
sudo zypper list-updates | grep -i kernel
The update only takes effect after the reboot. Install first, read what the package manager is going to remove or replace, and only reboot once the installation finishes without errors.
⚠️ VPS: before rebooting, confirm that you have access to the provider's emergency console. If the new kernel doesn't boot, that's how you select the previous kernel.
# Debian / Ubuntu / Mint
sudo apt update && sudo apt full-upgrade # confira a lista antes de responder "S"
# RHEL / AlmaLinux / Rocky / Oracle / Fedora / Amazon Linux 2023
sudo dnf upgrade --refresh
# Amazon Linux 2
sudo yum update
# openSUSE / SLES
sudo zypper refresh && sudo zypper update
After it finishes without error: sudo reboot.
After the reboot, check that the running kernel is the patched one:
# Ubuntu / Mint (a versão aparece no próprio nome)
uname -r # ex.: 6.8.0-149-generic ou mais novo, na MESMA variante
# Debian (uname -r mostra só a ABI, como 6.1.0-xx-amd64)
uname -v # ex.: "... Debian 6.1.190-1 ..." ou mais novo na mesma linha
# RHEL e derivados / Oracle / Amazon Linux
uname -r # ex.: 5.14.0-687.64.1.el9_8.x86_64 ou mais novo
rpm -q kernel # kernels instalados
# openSUSE / SLES
uname -r
rpm -q kernel-default
If the installed kernel is the patched one but uname -r/uname -v still shows the old one, a reboot is needed. ls /var/run/reboot-required (Debian/Ubuntu) and sudo needs-restarting -r (RHEL and derivatives) help you remember, but the absence of a warning does not prove you are patched. What proves it is the comparison above.