@brucexu_eth: Following up on the Linux kernel vulnerability CVE-2026-98432 I mentioned yesterday. This hole is more serious than I initially thought — if you run your own servers, I'd suggest dealing with it today. Feel free to throw this X post at your Agent. Why it's serious: - Wide scope: all kernels from Linux 4.4 onward are affe

X AI KOLs Timeline News

Summary

CVE-2026-98432 is a use-after-free vulnerability in the IPv4 TCP handshake path affecting all kernels from Linux 4.4 onward. It can be triggered without authentication via crafted packets carrying IP options, causing kernel crashes, memory leaks, or remote code execution (RCE has already been demonstrated in MPTCP environments). Ubuntu fixes are still in progress, and AWS states that upgrading the kernel and rebooting is the only complete remediation.

Following up on the Linux kernel vulnerability CVE-2026-98432 I mentioned yesterday. This hole is more serious than I first thought — if you run your own servers, I'd recommend handling it today. Feel free to throw this X post at your Agent. Why it's serious: - Wide scope: all kernels from Linux 4.4 onward are affected, which basically means every Linux server still in use. - No login required: as long as the server has even one publicly exposed IPv4 TCP port, an attacker can hit it by sending a few crafted packets. Possible consequences are kernel crashes, memory leaks, or memory corruption. - Remote code execution has already been achieved: researchers demonstrated unauthenticated RCE on machines running MPTCP. Ubuntu has MPTCP enabled by default. - No patch yet: as of today, the fixed kernels for Ubuntu 22.04 / 24.04 / 26.04 are still marked "fix in progress", so installing the latest kernel doesn't help either. The AWS advisory puts it bluntly: only upgrading the kernel and rebooting counts as a complete fix. Here's what I've done (5 machines in total, across bare metal and VPS): 1. Block the entry point first → Use nftables to drop all IPv4 TCP packets carrying IP options → Normal traffic almost never carries IP options, so there's essentially no side effect → Tested on every machine: connections with options are blocked, regular SSH works fine 2. Turn off MPTCP → net.mptcp.enabled=0, written into sysctl.d so it still applies after a reboot → This step only reduces the preconditions for exploitation; the vulnerability itself remains 3. Close unnecessary public ports → Disabled public SSH 22 on 3 VPS, using Tailscale SSH only → Basically all ports are shut 4. Wait for the patch → Automatically check Ubuntu's fix status once a day, and get notified the moment it ships so I can upgrade and reboot A few easy pitfalls: - Firewall rules disappear on reboot. Don't reboot casually before the patch is out — and even if you do, you can't apply the fix. - Changing the SSH port number is essentially useless against this hole. The vulnerability is in the kernel's TCP handshake, so any open port can serve as an entry point, and a full port scan only takes a few minutes. - Set up an automatic rollback before closing 22. My approach: schedule a timer that re-opens access automatically after 5 minutes, confirm Tailscale can connect, then cancel it — to avoid locking myself out. - If you use Coolify, don't delete the rule allowing Docker's internal network to reach port 22 on the host, or your deployments will break. - Ports like 80/443 have to stay open, so until the patch arrives, the drop rule from step 1 is what actually does the work. References: AWS advisory https://aws.amazon.com/security/security-bulletins/2026-160-aws/… Ubuntu fix status https://ubuntu.com/security/CVE-2026-98432…
Original Article
View Cached Full Text

Cached at: 11/03/26, 04:23 AM

Follow-up on the Linux kernel vulnerability CVE-2026-98432 I mentioned yesterday. This bug is more serious than I initially thought — if you run your own servers, I’d recommend dealing with it today. Feel free to hand this post off to your agent.

Why it’s serious:

  • Wide scope: all Linux kernels since 4.4 are affected, which basically means every Linux server still in use.
  • No login required: as long as the server has one publicly exposed IPv4 TCP port, an attacker can hit it by sending a few crafted packets. Possible outcomes are kernel crashes, memory leaks, or memory corruption.
  • Remote code execution has already been demonstrated: researchers have shown unauthenticated remote code execution against machines with MPTCP enabled. Ubuntu has MPTCP enabled by default.
  • No patch yet: as of today, the fixed kernels for Ubuntu 22.04 / 24.04 / 26.04 are all still “fix in progress” — installing the latest kernel won’t help. The AWS bulletin puts it bluntly: the only complete remediation is upgrading the kernel and rebooting.

Here’s what I’ve done (5 machines in total, across bare metal and VPS):

  1. Block the entry point first → Use nftables to drop all IPv4 TCP packets carrying IP options → Normal traffic almost never carries IP options, so there’s essentially no side effect → Tested on every machine: connections with options are blocked, regular SSH works fine

  2. Disable MPTCP → net.mptcp.enabled=0, written into sysctl.d so it persists after reboot → This only reduces the conditions for exploitation; the vulnerability itself is still there

  3. Close unnecessary public-facing ports → Disabled public SSH port 22 on 3 VPS instances, Tailscale SSH only → Basically all ports closed

  4. Wait for the patch → Automatically check Ubuntu’s fix status once a day, and get notified as soon as it’s released so I can upgrade and reboot

A few easy pitfalls:

  • Firewall rules disappear on reboot. Don’t casually reboot before the patch is out — even if you do, you won’t be able to get the fixed kernel anyway.
  • Changing the SSH port number is essentially useless against this bug. The vulnerability is in the kernel’s TCP handshake, so any open port can serve as an entry point — scanning all ports takes just a few minutes.
  • Set up automatic rollback before closing port 22. My approach: set a timer that automatically re-allows access after 5 minutes, confirm Tailscale can connect, then cancel it — so I don’t lock myself out.
  • If you use Coolify, don’t delete the rule allowing Docker’s internal network to reach local port 22, or your deployments will break.
  • Ports like 80/443 must stay open for business use, so until the patch arrives, the rule from step 1 is what actually does the work.

References: AWS bulletin https://aws.amazon.com/security/security-bulletins/2026-160-aws/… Ubuntu fix status https://ubuntu.com/security/CVE-2026-98432…


CVE-2026-98432 - Linux kernel IPv4 TCP use-after-free Issue

Source: https://aws.amazon.com/security/security-bulletins/2026-160-aws/ **Bulletin ID:**2026-160-AWS **Scope:**AWS **Content Type:**Important (requires attention) **Publication Date:**10/30/2026 22:15 PM PDT **Last Updated Date:**11/02/2026 15:00 PM PST

Summary:

AWS is aware ofCVE-2026-98432 (https://nvd.nist.gov/vuln/detail/CVE-2026-98432), a memory issue in the Linux kernel IPv4 TCP handshake path affecting kernel versions 4.4 and later. Under specific conditions, a remote, unauthenticated third-party could send crafted IPv4 TCP packets that carry IP options to an affected listener. This could result in a kernel crash, disclosure of kernel memory, or memory corruption. Researchers have demonstrated unauthenticated remote code execution against hosts with a Multipath TCP (MPTCP) listener. We have no evidence that this issue has been leveraged at this time. We will update this bulletin as more information becomes available.

Current Mitigation Status:

Amazon Linux

Amazon Linux 2 and Amazon Linux 2023 kernel packages for the resolution of CVE-2026-98432 are available. Customers should update their kernel packages and reboot. Kernel versions kernel-4.14, kernel-5.4, kernel-5.10, kernel-5.15, kernel-6.1, kernel-6.12, & kernel-6.18: Available now.

Advisories: ALAS2-2026-4065, ALAS2KERNEL-5.4-2026-135, ALAS2KERNEL-5.10-2026-137, ALAS2KERNEL-5.15-2026-120, ALAS2023-2026-3365, ALAS2023-2026-3335, ALAS2023-2026-3251.

To update:

# Amazon Linux 2 sudo yum update kernel && sudo reboot

# Amazon Linux 2023 Kernel 6.1 sudo dnf update kernel --releasever=latest && sudo reboot

# Amazon Linux 2023 Kernel 6.12 sudo dnf update kernel6.12 --releasever=latest && sudo reboot

# Amazon Linux 2023 Kernel 6.18 sudo dnf update kernel6.18 --releasever=latest && sudo reboot

Amazon Linux 2023 instances that are locked to a release version must use release 2023.12.20261102 or later to receive the updated kernel.

Amazon EC2

Customers running self-managed Linux instances on Amazon EC2 are responsible for updating the kernel on those instances. If you run Amazon Linux, update the kernel package as described above. If you run another Linux distribution, follow your distribution’s guidance for applying the fix when it becomes available.

After updating the kernel, a reboot is required for the fix to take effect. A kernel update and reboot is the only complete remediation for this issue.

AWS Web Application Firewall, Application Load Balancer, Classic Load Balancer, TLS Listeners on Network Load Balancer, Cloud Front, API Gateway

Customers using the above services do not receive TCP connections from untrusted sources directly when following best practices. AWS is applying updates to the underlying infrastructure of these services and no immediate customer action is required if you are using these services. We still recommend customers update their self-managed instances behind these services within the next 30 days.

Network Load Balancer (TCP Listeners) and Amazon Global Accelerator

Network Load Balancer TCP listeners pass client packets, including IP options, to targets. Customers running Linux targets behind Network Load Balancer TCP listeners, or Linux endpoints behind AWS Global Accelerator, should update the kernel on those targets and reboot, or apply the interim steps below until they can.

Amazon EKS

Amazon EKS has released updated EKS-optimized Amazon Linux 2023 AMIs (release v20261031 (https://github.com/awslabs/amazon-eks-ami/releases/tag/v20261031)) that address this issue. Customers using managed node groups, self-managed nodes, or Karpenter with these AMIs should update their nodes to v20261031 or later.

Amazon EKS released updated EKS Auto Mode AMIs on October 31, 2026. EKS Auto Mode automatically replaces existing nodes with nodes running the updated AMI, subject to your NodePool disruption budgets. No customer action is required for EKS Auto Mode. EKS Auto Mode AMIs are named in the form “Bottlerocket (EKS Auto, Standard) 2026.10.31”. To check which AMI your nodes are running, run the command kubectl get node -o wide and compare the OS-IMAGE column.

Amazon EKS Fargate Pods launched after November 1, 2026, 9:00 AM PST (November 1, 2026, 5:00 PM UTC) run on the patched platform. Amazon EKS replaces pods that were already running within 14 days as part of our routinesecurity patching cycle (https://docs.aws.amazon.com/eks/latest/userguide/fargate-pod-patching.html).

Amazon ECS

Customers running ECS on EC2 should update the kernel on their container instances and reboot, or replace them with instances launched from the latest ECS-optimized AMI (release 20261031 (https://github.com/aws/amazon-ecs-ami/releases/tag/20261031)).

  • Fargate: AWS has released a patched platform version. All new tasks launched after November 1, 2026, 9:00 AM PST (November 1, 2026, 5:00 PM UTC) use the patched platform version. Existing tasks are retired per your task retirement settings, or you can replace them sooner as described inTask retirement and maintenance for AWS Fargate (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-maintenance.html).
  • ECS Managed Instances: AWS has released an updated AMI, and new instances launched after the same time use the patched AMI. Existing instances are drained 14 days after launch, or earlier to align with your event windows (Patching in Amazon ECS Managed Instances (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/managed-instances-patching.html)). To update immediately,drain them manually (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container-instance-draining.html).

Bottlerocket

The patched Bottlerocket kernel has been released. Updated Bottlerocket AMIs with the patched kernel are expected to be available beginning November 02, 2026. We recommend customers update to the latest Bottlerocket AMI when available.

AWS Lambda

Lambda workloads are not affected by this issue. CVE-2026-98432 requires an actor to send a specially crafted network packet to a publicly reachable IPv4 TCP port on an affected host. Lambda functions do not expose public IPv4 TCP ports, so there is no path for an external party to reach your function’s execution environment with the type of traffic needed to trigger this issue. No action is required on your part.

As a defense-in-depth measure, we are proactively applying the kernel patch to the Lambda service infrastructure.

Amazon Lightsail

Customers running self-managed Linux instances on Amazon Lightsail are responsible for updating the kernel on those instances. If you run Amazon Linux, update the kernel package as described above. If you run another Linux distribution, follow your distribution’s guidance for applying the fix when it becomes available.

After updating the kernel, a reboot is required for the fix to take effect. A kernel update and reboot is the only complete remediation for this issue.

VPC Endpoints (PrivateLink)

Customers running Linux targets behind AWS PrivateLink endpoint services should update the kernel on those targets and reboot, or apply the interim steps below until they can.

VPC Lattice

Customers running Layer 4 (TCP) targets on Linux behind VPC Lattice should update the kernel on those targets and reboot, or apply the interim steps provided below until they can.

RDS / Aurora

RDS / Aurora customers need to make sure that the database ports are not exposed to the internet. Additionally, we are deploying mitigations worldwide to prevent exploitation on your database hosts. Long term remediation will be for you to patch your database OS. This patch will be available Tuesday, November 3, 2026.

Neptune

Neptune customers need to make sure that the database ports are not exposed to the internet.

Redshift

Redshift is taking mitigation actions that are deploying worldwide to prevent leveraging on your cluster hosts. For long term remediation, Redshift Cluster OS patch will be available Monday, November 2, 2026.

Storage Gateway

We are expecting an update beginning November 03, 2026. We recommend customers update to the latest version when available.

AWS Cloud9

AWS Cloud9 EC2 environments install Amazon Linux and Ubuntu security updates automatically, but an updated kernel takes effect only after the environment restarts. After the update installs, customers should restart each environment’s EC2 instance, or stop the environment and start it again. Canonical has not yet released a fixed kernel for Ubuntu. Customers using Ubuntu environments should restart them after the fixed kernel installs. Customers using AWS Cloud9 SSH environments are responsible for updating the kernel on their own servers.

Amazon GameLift

Amazon GameLift Servers is releasing updated Amazon Linux 2 and Amazon Linux 2023 AMIs that include the patched kernel. Existing managed EC2 and container fleets continue to use the AMI they were created with. To receive the fix, create a new fleet after the updated AMIs are available and move your game session traffic to it, for example by updating your game session queue destinations or aliases. Recreating the fleet is the only way to make sure every instance has the fix, because fleets launch new instances from the AMI they were created with. We’ll update this bulletin when the updated AMIs are available in all Regions. Fleets running Windows are not affected.

Customers using Anywhere fleets manage their own operating system and should update the kernel and reboot, as described for Amazon EC2 above.

Note: The fix is not yet available for Amazon GameLift Servers managed fleets. Fleets you create now will not include the patched kernel. We expect updated AMIs to be available in all Regions by November 04, 2026. We recommend waiting until this bulletin is updated with a confirmation that the fix is available before you create replacement fleets.

Amazon WorkSpaces

Amazon WorkSpaces Windows bundles are not affected by this issue. Linux WorkSpaces use affected Linux kernels and should be updated as fixed kernels become available from the applicable operating system vendor.

In the default WorkSpaces configuration, Linux WorkSpaces do not accept inbound connections from outside the WorkSpace, and the default WorkSpaces security group allows no inbound access. Customer impact increases if customers have opened inbound ports to Linux WorkSpaces, such as SSH, or run their own TCP services, especially MPTCP-enabled services.

Amazon WorkSpaces Personal instances with Amazon Linux 2 can receive the fixed Amazon Linux kernel through existing WorkSpaces maintenance mechanisms. Customers should ensure Linux WorkSpaces can reach their operating system update repositories and should restart WorkSpaces after fixed kernels are installed so the updated kernel is active.

Amazon WorkSpaces Applications fleets and image builders with Amazon Linux 2 can receive the fixed Amazon Linux kernel by creating an updated image through the AWS CLI or SDK, or by launching and updating an existing image builder or image, and then creating a new image from that. In both cases, customers should finish by updating their fleets to use the new image.

For third-party Linux distributions such as Ubuntu, Red Hat Enterprise Linux, and Rocky Linux, fixed kernel availability depends on the respective operating system vendor. Customers should monitor their vendor’s security advisories and apply updates when available. On Amazon WorkSpaces Personal instances running Ubuntu, installing a fixed kernel may not protect the running WorkSpace until the WorkSpace is restarted, unless the vendor provides an applicable livepatch that is installed and active.

AutoStop WorkSpaces that are stopped are not running and cannot be exploited while stopped; they will need to install updates and restart after they next start or during their maintenance window. Customers who disabled maintenance mode or restrict repository access should verify that updates are being applied.

Newly provisioned Linux WorkSpaces Personal instances install available operating system updates during provisioning. After fixed kernels are available from the relevant OS repository, newly created Linux WorkSpaces should start with the available fixed kernel after provisioning completes.

AWS Database Migration Service (AWS DMS)

AWS DMS replication instances, including those that run AWS DMS Serverless replications, do not accept inbound connections from customer networks or the internet, so there is no path for an external party to send them the traffic needed to trigger this issue.

As a defense-in-depth measure, AWS DMS will apply the patched kernel to all replication instances and to AWS DMS Serverless replications. The update will be available in all AWS Regions by November 2, 2026. AWS DMS will apply it during a weekly maintenance window, with a reboot. During the reboot, running tasks pause and resume, and tables still in full load restart. To choose when this happens, change the replication instance’s maintenance window.

To get the update sooner, check whether aws dms describe-pending-maintenance-actions lists an os-patch action for your replication instance. If it does, apply it now. This reboots the instance right away:

aws dms apply-pending-maintenance-action --replication-instance-arn --apply-action os-patch --opt-in-type immediate

Amazon MQ

Amazon MQ has released an updated host image with the patched kernel for Amazon MQ for RabbitMQ and Amazon MQ for ActiveMQ. Brokers created after November 2, 2026, 12:16 UTC use the patched kernel. Existing brokers are updated automatically during their next scheduled maintenance window, and no customer action is required. To apply the update sooner, change the broker’s maintenance window to an earlier time. Rebooting a broker does not apply this update. For more information, seeScheduling the maintenance window for an Amazon MQ broker (https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/maintaining-brokers.html).

Interim step for customers who cannot update immediately

Disable MPTCP by setting the kernel parameter net.mptcp.enabled=0, or set GODEBUG=multipathtcp=0 for applications built with Go 1.24 or later. This step reduces the conditions for running code on a host, but it does not resolve the issue. Updating the kernel and rebooting resolves the issue.

Customers can disable IP Options to mitigate this with an IP tables rule. An example is provided below:

iptables

Similar Articles

TCP Use-After-Free: CVE-2026-98432 / CVSS 9.8

Hacker News Top

Linux 河修复了 CVE-2026-98432,一个 CVSS 9.8 严重的 IPv4 TCP 握手 use-after-free 漏洞,可被远程未认证攻击者利用;Anthropic 的 Claude 生成了可远程 root 的 PoC,而 Ubuntu 和 RHEL 等主流发行版仍未发布修复补丁。

@interjc: 大的来了

X AI KOLs Timeline

Linux 内核 MPTCP TCP 缺陷被评为 9.8 CVSS,Anthropic 演示了可在服务器上以 root 权限执行命令的漏洞利用,Ubuntu 和 RHEL 尚未修复,而 Debian、Oracle 等已发布部分补丁。

@tobi: What a disaster

X AI KOLs Following

Linux's stable kernels shipped fixes for CVE-2026-98432, a critical (CVSS 9.8) use-after-free in the IPv4 TCP handshake reachable by remote unauthenticated attackers; Anthropic reported the bug and says its Claude model wrote a working remote root exploit, while Ubuntu and RHEL remain unfixed.

CVE-2026-98432: Linux TCP Use-After-Free Risk and Patch Validation

Hacker News Top

CVE-2026-98432 is a use-after-free in the Linux kernel's IPv4 TCP handshake path that could allow remote exploitation, with a Linux CNA CVSS of 9.8 and Red Hat's preliminary 8.1 score, while Anthropic's Frontier Red Team demonstrated remote root execution against an MPTCP listener; the article reviews patch validation and distribution-specific remediation steps.

Protecting against CVE-2026-98432

Lobsters Hottest

Go security team warns about CVE-2026-98432, a use-after-free bug in Linux kernel IPv4 TCP handling enabling RCE (exploit demonstrated by Anthropic via MPTCP listeners), recommending a patched kernel upgrade and detailing how to disable MPTCP defaults in Go programs.