CVE-2026-98432 in Proxmox VE

My plan is to fix the relevant bugs as quickly as possible. Bugs that are irrelevant to a particular environment can be skipped. If you blindly fix everything immediately, you can either hire a dedicated team or automate the fixes and hire a team to ensure all services function flawlessly after each patch. In a larger, 24/7 environment, this could be more complex than it initially appears.

Unfortunately this approach doesn't work anymore in 2026. Every kernel update contains hundreds if not thousands of patches for cves (https://www.phoronix.com/news/Linux-Kernel-CVEs-Nearly-2000 ). So whether you want to check whether an update applies to your environment or whether it might contain breakage: In both cases you need a dedicated team and still might get bite back by some missed issue. Shall Proxmox developers publish 2000 security advisorys per updated kernel because otherwise moronic change boards won't accept an update due to potential breakage? Have fun checking what's applicable to your environment then. Or do you happen to have a kernel security researcher on call who is able to give you an outcome which of the 2000 fixed CVEs of the last kernel applies to you or not under 24 hours (the time you need today to apply a patch before bad actors start exploiting the vulnerability: https://zerodayclock.com/)?

With other words: "Only apply needed patches" doesn't work either anymore, all you can do is to develop strategies to minimize breakage. Depending on your budget and other constraints this can be strategies for a fast rollback (by having a spare server with an older version), utilicing high-availability (on application and hypervisor level so you can first apply the patches to one node/vm, then to the others), rebuild systems automatically (see https://zerodayclock.com/call-to-action#stop-patching-start-rebuilding ) or whatever works for you.

But thinking, that "patch-management" aka "only apply needed fixes" still works in 2026 is at best naive wishful thinking and at worse gross negelect.
And yes I'm aware that in practice it's hard to do right in most corporate environments, but admitting the broken state of most IT environments (tbh including the one I work with for a living) is a start to actually fix this mess instead of working around of it.
 
Last edited:
Does anyone know whether CVE-2026-98432 can actually be abused by a VM to break guest isolation / gain access to the host? Or is that not a risk for this CVE?
We already patched this CVE on all guests - but not the host. Not sure if I actually must patch this or if there isn't really any risk at the moment.
 
the known PoC requires MTCP, the vulnerability itself does not. rolling out the fixed kernel on the host is very much advised.
 
Hello,
It is safe in a PVE cluster to apply the mitigation setting up net.mptcp.enabled=0 and restarting the process related to the existing sockets?
Thank you
 
Hello,
It is safe in a PVE cluster to apply the mitigation setting up net.mptcp.enabled=0 and restarting the process related to the existing sockets?
Thank you
If you're asking whether it's "safe" in the sense of whether Proxmox uses MPTCP, then yes: at least out of the box, Proxmox doesn't use any MPTCP sockets.

You can check this with ss -Mlnp. No output means no MPTCP sockets, means nothing should break if you disable it.

However, you should still apply the patch to eliminate the vulnerability and avoid being exposed to potential attacks!
 
Hello @proxuser77 , yes my question was related if proxmox uses MPTCP.
I did run the command and I have some sockets MPTCP, but not related to Proxmox processes. So I assume it is safe to apply this workarround until I'm able to apply the patch.
Thank you
 
Hello @proxuser77 , yes my question was related if proxmox uses MPTCP.
I did run the command and I have some sockets MPTCP, but not related to Proxmox processes. So I assume it is safe to apply this workarround until I'm able to apply the patch.
Thank you
Sorry, how are we supposed to know that? Obviously, something must have been enabled or installed on your server that makes use of it. Whether that component is actually needed or not is ultimately for you to decide.

And just to be absolutely clear once again: this mitigation only protects against this specific proof-of-concept exploit. There's no way of knowing whether other exploits already exist that could exploit the vulnerability in different ways.

So please, update to a patched kernel ASAP!