CVE-2026-99288 (NoisyTCP) status in Proxmox

We need some kind of query tool for this. Every other day another question about CVEs
Yes, that would certainly be helpful, although someone would then need to maintain and update it in a timely manner. ;)

However, based on my understanding of this announcement, Proxmox will start basing their kernels directly on upstream starting with 7.3. So, in principle, one could simply subscribe to the Linux CVE mailing list to see the relevant CVEs in each version: https://docs.kernel.org/process/cve.html#cves.
 
Small addition, since the question comes up a lot: the fix was actually picked a bit earlier than 7.0.14-30.

The patch "inet: reject unhashed sockets during established lookups" entered pve-kernel on 6 November with the commit "cherry-pick network fixes, disallow payload rewrites in user namespaces", so it first shipped in 7.0.14-29.

The commit linked above only rebased it.
That also means the enterprise repository, currently at 7.0.14-29, already has it.

The changelog does not mention the CVE because the ID was only published on 10 November, after the kernel was released. The 7.0.14-29 entry lists it as "TCP: a crash in socket lookups under load with SYN cookies".

So: running 7.0.14-29 or newer means you are covered. Check with `uname -r`, as having the package installed is not enough until the node has rebooted into it.
 
  • Like
Reactions: EllerholdAG
However, based on my understanding of this announcement, Proxmox will start basing their kernels directly on upstream starting with 7.3. So, in principle, one could simply subscribe to the Linux CVE mailing list to see the relevant CVEs in each version: https://docs.kernel.org/process/cve.html#cves.
Oh nice. I just read the headline, not that they switch (again).

There is a project called https://proxmoxcve.com but the notification there only works if the advisories are posted correctly in the forum here, so...
Nice.