TL;DR
A critical flaw in the Linux kernel’s networking code was disclosed on October 29, 2026. It is tracked as CVE-2026-98432 and scored 9.8 out of 10 for severity. It can be triggered remotely, with no login and no action from your visitors, and it affects almost any internet-facing Linux server, including the servers most WordPress sites run on. If your site is hosted with us, the servers have already been patched and you need to do nothing. If you run your own server (VPS or cloud), you need to update the kernel and reboot.
What happened
Researchers disclosed a use-after-free bug in the part of the Linux kernel that sets up new IPv4 TCP connections. In plain terms, the kernel can be tricked into using a piece of memory after it has already been released, which can lead to a crash or, in the worst case, an attacker taking control of the server.
This is not a WordPress bug, and it is not a plugin or theme problem. It sits underneath WordPress, in the operating system itself. Because the flaw is in the code that accepts incoming connections, any Linux server that answers requests from the internet is potentially in scope. Kernels going back to version 4.4, released in early 2016, are affected.
The kernel security team rated it 9.8 (Critical). Some Linux distributions have scored it lower in their own advisories, but with a remote, unauthenticated attack path, the safe approach is to treat it as urgent. Public research reportedly describes a working exploit for some server configurations, so waiting is not a great option.
Which versions are fixed
The fix is available in these stable kernel releases:
- 5.10.272
- 5.15.223
- 6.1.190
- 6.6.159
- 6.12.113
- 6.18.56
- 7.2.10
As of October 30, several major Linux distributions had not yet shipped a fixed kernel, so availability depends on which distribution your server runs. Check your distribution’s security advisory for CVE-2026-98432.
What to do
- Find out who manages your server. If you pay a host for managed WordPress or shared hosting, the host patches the kernel, not you. If you have a VPS, cloud server, or dedicated server that you (or your developer) maintain, that job is yours.
- Ask your host if they have patched. A short support message is enough: “Has CVE-2026-98432 been addressed on the server hosting my site?” Many hosts use live patching, which fixes the running kernel without a reboot or any downtime for your site.
- If you manage your own server, update the kernel. Check your distribution’s advisory, install the fixed kernel as soon as it is available, and schedule the reboot it requires. If your distribution offers a live patching service, confirm that it covers this CVE. Start with any server that accepts connections from the internet.
- Keep the usual layers in place. Current backups, WordPress core, plugins, and themes all up to date, and strong admin passwords with two-factor authentication. A kernel patch protects the server, but it does not protect a site from an outdated plugin.
- Watch for odd behaviour. Unexpected slowdowns, unexplained restarts, or new admin users are worth a closer look. Tell your host or us if you see any of them.
What does this mean for my site?
Our clients do not need to do anything. The servers hosting your sites were live patched on October 29, 2026, the same day the flaw became public. The patch updates the running kernel in memory, so there were no reboots and no downtime for your site or its database. If your site is hosted somewhere other than with us, ask your host to confirm in writing that CVE-2026-98432 has been addressed.
For WP Lifeline Care Plan clients
If you are on a WP Lifeline Care Plan, you do not need to do anything. We are tracking this vulnerability, confirming patch status with the servers your sites run on, and following up directly if anything needs your attention.
Not on a Care Plan and not sure where you stand?
If you are not sure who manages your server, whether it has been patched, or whether your site is exposed, get in touch. We can check your hosting setup, follow up with your host for you, and help you move to a safer arrangement if your current one is not keeping up.
Get started here!
Not sure whether your site is covered? Contact us and we will take a look.