Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article5 min readViews1

Linux Kernel Vulnerability CVE-2026-98432: What to Check on VPS and Dedicated Servers

A flaw in IPv4 TCP affects the Linux kernel. Patches are already available for several packages, while major Ubuntu branches are still awaiting updates. We explain the safe verification procedure.

Comments 0

Orange segment next to a damaged outer ring of an abstract metallic object
In this article

On October 30, 2026, Linux vendors updated the details for CVE-2026-98432, a flaw in the kernel network code that can be triggered remotely via IPv4 TCP. VPS/VDS and dedicated server owners should check not just the kernel version, but the status of the specific package from the OS provider and the actual kernel version running. Patches have not yet been released for all distributions and branches.

Changes in Risk Assessment

In the Canonical card, CVSS 9.8 and Ubuntu High priority are listed. The error occurs when one processor frees socket parameter data while another is still using it during TCP connection processing. Such access to already freed memory can lead to a crash or kernel memory corruption.

Red Hat rates the vulnerability as Critical for affected RHEL releases: a remote unauthenticated attacker can cause kernel memory corruption or an immediate crash via standard IPv4 TCP traffic. Reliable code execution requires more complex memory management, so the vendor's criticality rating should not be interpreted as a guarantee that every accessible server can be compromised.

Anthropic researchers demonstrated remote command execution with root privileges on a server with a listening MPTCP socket. This is a laboratory demonstration, not confirmation of widespread breaches. It illustrates a potential severe scenario but does not replace applicability testing for a specific OS, package, and configuration.

For a website owner, the practical takeaway is clear: updating PHP, 1C-Bitrix, or a CMS does not fix this issue because it resides in the OS kernel. On a self-administered VPS/VDS or dedicated server, the administrator performs the check; on shared virtual hosting, you must request the status of the host nodes from the provider. The absence of MPTCP does not prove safety: it relates only to the published code execution demonstration, whereas vendors describe other consequences for IPv4 TCP.

Patches Depend on Distribution and Package

For the main package with the exact name linux in Ubuntu 22.04 LTS, 24.04 LTS, 26.04 LTS, and 26.10, the status at the time of checking is Vulnerable, work in progress. Cloud, HWE, and other kernel variants have separate status lines. The number of the pending package next to the status does not mean the update has already been released or installed.

In the Amazon Linux bulletin dated October 30, the following Amazon Linux 2 and Amazon Linux 2023 packages are listed as Fixed, including kernel, kernel6.12, and kernel6.18. This does not justify assuming that a server running a different OS or branch is patched: the status applies only to the specified packages and release dates.

The initial Linux CVE team announcement listed fixes in upstream branches, including 6.12.113, 6.18.56, and 7.2.10. These version numbers cannot be directly compared to Ubuntu, RHEL, or Amazon Linux package versions: distributions backport fixes into their own branches. The kernel team recommends updating the entire supported branch rather than manually selecting individual commits.

What a VPS or Server Owner Should Do

  • Compile a list of servers, distributions, kernel packages, and the actually running kernels; separately note IPv4 TCP services accessible from outside.
  • Cross-reference CVEs with the status of your specific package in the vendor's official bulletin. Do not transfer a Fixed status from a neighboring branch to your own.
  • If a fix is available, coordinate the installation and required reboot according to the OS vendor's procedure. Before starting work, verify the currency of backups and the rollback plan.
  • After rebooting, confirm that the updated kernel is running and that the website, email, control panels, integrations, and backup systems are operational.
  • If the fix is still in preparation, schedule a re-check of the bulletin and agree with the administrator on temporarily reducing network availability without disrupting required business connections.

Do not disable network functions or reboot the production infrastructure based on a universal command from a news post. A restriction may disrupt required connections and does not replace a fix. An updated package on disk also does not prove that the server is already using the patched kernel.

Result criteria

  • The official bulletin shows Fixed or Not affected for the exact package and OS release.
  • The actually running kernel corresponds to the installed patched package; this is verified after the required reboot.
  • External and internal services have passed availability checks, and backup jobs completed without new errors.
  • If a patch is not yet available, the responsible person, the date of the next check, and temporary restrictions accounting for site dependencies are recorded.

Information verified on October 31, 2026. The CVE record was published on October 15, the investigation on October 27, the Ubuntu card updated on October 30, and Amazon Linux released additional patches on October 30. The material does not assert that a specific General iT or client server was compromised; the status is determined separately by OS, package, and running kernel.

Discussion 0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.