---
title: 'cve-2026-98432-vulnerability-in-the-linux-kernel-what-server-owners-should-do'
description: 'CVE-2026-98432 Linux kernel vulnerability: understand the security risk and learn what steps server owners should take to protect their systems.'
image: 'https://cdn.zomro.com/uploads/blog/a48%40server-panel.net/2026/10/31/en-cracked-core1x_q50.jpg'
---

![opened image]()

  * [Zomro](https://zomro.com/)
  * [FAQ](https://zomro.com/blog/faq/)
  * CVE-2026-98432: Linux kernel vulnerability. What server owners should do 



# CVE-2026-98432: Linux kernel vulnerability. What server owners should do

31-10-2026

![](https://cdn.zomro.com/uploads/blog/a48%40server-panel.net/2026/10/31/en-cracked-core1x_q50.jpg)

A bug, CVE-2026-98432, with a score of 9.8 out of 10 has been found in the Linux kernel. It is located in the part of the system that accepts new connections to the server. The bug is about ten years old: it is present in all kernels starting from version 4.4.

On October 27, Anthropic researchers showed that it can be used to gain full control over a server with a certain network configuration remotely, without a password and without any action on your part. To do this, their AI model wrote a working attack program on its own.

> A fix is already available in updated kernels. But at the time of writing, there are no ready-made packages for Ubuntu and RHEL yet. Below, we explain how to check your server, how to update, and how to protect yourself until the update is available.

## What is the Linux kernel

The kernel is the foundation of the operating system. All of the server's programs run on top of it: the website, the database, the mail, the control panel.

Imagine an apartment building. The apartments are your programs. The kernel is the foundation, the elevator, and the front door. If there is a crack in the foundation, it does not matter what locks are on the apartments.

That is why kernel vulnerabilities are especially dangerous. They are not visible from the website, dependency checks do not find them, and they affect all programs on the server at once. Even Docker containers do not protect you: all containers share a single kernel.

## What happened

Every connection to a server begins with a three-step “handshake”. The client says “hello”, the server replies “hello, I hear you”, and the client confirms. Only after that does the data exchange begin.

In the first “hello”, additional service marks can be passed, the so-called IP options. In everyday use, almost nobody uses them. The server writes these marks onto a card and uses them when it replies.

**What the bug is.** Imagine two waiters working with the same order card. The first one closes the order and throws the card away. At that moment, the second one is still reading it in order to respond to a guest who repeated their question. He is reading a discarded slip of paper that could have anything written on it.

The kernel works the same way: one part of the system frees the memory holding the marks, while another part keeps using it in that same second. An attacker can deliberately trigger this situation and plant their own data in the freed memory.

**Timeline:**

Date |  Event  
---|---  
October 27 |  Anthropic demonstrated a working attack that gains full control over a server  
October 24 |  The kernel team rated the vulnerability 9.8 out of 10  
October 15 |  The vulnerability was assigned a CVE number  
October 5 |  The fix was merged into the Linux kernel  
  
**About the Anthropic attack.** The AI model wrote a program on its own that went from the first memory leak to full control over the server in 53 minutes. The attack worked against servers where MPTCP is enabled. This is an extension of TCP that allows a single connection to run over several networks at once. Programs written in Go enable it by default starting from version 1.24.

> As of October 29, no real-world attacks have been recorded. Distributions rate the vulnerability somewhat lower: Red Hat, Oracle, and SUSE give it 8.1 out of 10. But that is still a high level.

## Who is affected

**Almost any Linux server that accepts connections over IPv4.** Websites, mail, databases, VPNs, game servers, APIs. If a server can be reached on at least one port, it is at risk.

Not affected:

  * IPv6 connections. There the kernel copies the marks, and the bug does not occur. But if the server also responds over IPv4, this does not save it;
  * kernels older than version 4.4 and RHEL 7.



**Status of fixes in distributions as of October 30:**

Distribution |  Status  
---|---  
Debian 12 and 13 |  Fixed  
SUSE SLES 16 |  Fixed  
Oracle Linux (UEK kernel) |  Fixed  
Amazon Linux 2023 (kernels 6.12 and 6.18) |  Fixed  
Ubuntu |  No fix yet  
RHEL 8, 9, 10 |  No fix yet  
AlmaLinux, Rocky Linux |  Usually released after RHEL  
  
If you use Ubuntu, AlmaLinux, or Rocky Linux, be sure to read step 3 on temporary protection.

## Find out your kernel version
    
    
    uname -r

The output will look like `6.1.0-28-amd64` or `6.8.0-71-generic`. The first digits are the kernel branch.

Fixed versions of the main branches:

Branch |  Safe version  
---|---  
5.10 |  5.10.272 and above  
5.15 |  5.15.223 and above  
6.1 |  6.1.190 and above  
6.6 |  6.6.159 and above  
6.12 |  6.12.113 and above  
6.18 |  6.18.56 and above  
7.2 |  7.2.10 and above  
7.3 |  Fixed  
  
> **Important.** In Ubuntu, RHEL, and other systems, the kernel numbering is their own and does not match this table. For example, `6.8.0-71-generic` in Ubuntu says nothing about whether the fix is present. So it is more reliable to look at your distribution's CVE page (links at the end of the article).

**Check whether MPTCP is enabled:**
    
    
    sysctl net.mptcp.enabled

If the answer is `= 1`, programs on the server can use it. These are exactly the kind of servers Anthropic attacked.

## Update the kernel and reboot

If a fix has already been released for your system, install it:

**Debian and Ubuntu:**
    
    
    sudo apt update
    sudo apt upgrade
    sudo reboot

On Debian 13 you need package version `linux 6.12.113-1` or newer, on Debian 12 `linux 6.1.190-1` or newer. Make sure the security updates repository is enabled in your package sources.

**AlmaLinux, Rocky Linux, RHEL, Oracle Linux:**
    
    
    sudo dnf upgrade --refresh
    sudo reboot

**Without a reboot, the new kernel will not take effect.** It is like swapping the engine but not restarting the car. It keeps running on the old one. After the reboot, run `uname -r` again and make sure the version has changed.

**Containers.** Updating a Docker image does not change the kernel. You need to update the server itself on which the containers run.

**Livepatch.** If you have Ubuntu Pro with Livepatch or a similar service, check whether a “live” patch has been released for this vulnerability. It closes the hole without a reboot, but you still need to do a regular kernel update later.

## Temporary protection until an update is available

If there is no fix for your system yet, you can significantly reduce the risk. This is not a replacement for the update, but a fence around a construction site until the new foundation is poured.

### 1\. Disable MPTCP

Almost nobody needs it on ordinary servers. And the demonstrated attack worked precisely through it.
    
    
    sudo sysctl -w net.mptcp.enabled=0
    echo "net.mptcp.enabled = 0" | sudo tee /etc/sysctl.d/99-disable-mptcp.conf

The first command disables MPTCP right now, the second saves the setting across reboots.

### 2\. Drop packets with IP options

The bug is triggered only on connections that contain those very service marks. Normal traffic does not contain them. So such packets can simply be dropped.

For iptables:
    
    
    sudo iptables -I INPUT -p tcp -m u32 --u32 "0>>24&0xF=6:15" -j DROP

For nftables:
    
    
    sudo nft add table inet cvefix
    sudo nft add chain inet cvefix input '{ type filter hook input priority -10; }'
    sudo nft add rule inet cvefix input ip hdrlength gt 5 meta l4proto tcp drop

First, test the rule on a test server. If your website and services work as usual, apply it on production servers.

Such rules are reset after a reboot. To make them persistent, add them to your firewall configuration, for example via the `iptables-persistent` package or the `/etc/nftables.conf` file.

### 3\. Close unnecessary ports

Every open port is a door through which an attack can be attempted. Leave open only the ones you need. Databases, control panels, and service tools are best opened only to your own IP addresses.

> **It is important to understand.** Disabling MPTCP makes the server less vulnerable, but not invulnerable. The bug itself is reachable through any IPv4 port. So as soon as a fix is released for your system, update the kernel.

## Checklist

  * Found out the kernel version with the `uname -r` command
  * Checked on the distribution's page whether a fix has been released
  * If it has, updated the kernel and rebooted the server
  * If not, disabled MPTCP
  * Added a rule that drops packets with IP options
  * Closed unnecessary ports
  * Set a reminder to check for the fix release for Ubuntu or RHEL



## Don't want to deal with it yourself?

A kernel update requires a reboot, which means a short downtime. Firewall rules are easy to write in a way that makes the server stop responding. And someone also needs to be assigned to wait for the fix for Ubuntu or RHEL and not forget to install it.

For such cases, Zomro has two options.

### SOD: we will protect the server for you

Our system administrator will:

  * check the kernel version and the fix status for your system;
  * disable MPTCP and add a temporary firewall rule;
  * close unnecessary ports;
  * update the kernel and reboot the server at a time convenient for you, as soon as the fix is released.



Cost: €12.50 for every 15 minutes of work.

Order server protection

### Premium: fast help when you need it

If the server does not come back up after a reboot, all the websites on it are down. For a regular support ticket, a response can take up to 10 hours. With Premium, we respond within 5 to 30 minutes.

New vulnerabilities appear every week. With Premium, you will not have to deal with them alone.

[Get Premium](http://zomro.com/paid-support-services)

Table of contents

  * What is the Linux kernel
  * What happened
  * Who is affected
  * Find out your kernel version
  * Update the kernel and reboot
  * Temporary protection until an update is available
  * Checklist
  * Don't want to deal with it yourself?



Similar articles:

[How to connect to a Docker container via sFTP](https://zomro.com/blog/faq/306-how-to-connect-to-a-docker-container-via-sftp) [How to enable previous session restore on Windows Server 2016, 2019?](https://zomro.com/blog/faq/311-kak-vkljuchit-vosstanovlenie-predyduschej-sessii-na-servere-windows-server-2016-2019) [Why you need to disable UDP for RDP connections to Windows Server](https://zomro.com/blog/faq/427-otklyuchenie-udp-dlya-rdp-podklyuchenij-k-windows-server) [PHP System Garbage Collector on Linux](https://zomro.com/blog/faq/372-php-system-garbage-collector-on-linux) [Error 504 524 Gateway Timeout (solved)](https://zomro.com/blog/faq/226-oshibka-504-524-gateway-timeout)

[ Virtual hosting from €3.98/mon ](/virtual)
