Recent content by fabian

no, those kernel series (and their associated product releases) are all EOL and do not get any updates anymore.

because the changelog predates the CVE assignment by almost a week: changelog bump on 09.10: https://git.proxmox.com/?p=pve-kernel.git;a=commitdiff;h=316d1680efe8277d3ce6d8b2cf2e19c838e9173a CVE assignment on 15.10...

we will consider how to improve the notification behaviour, thank you for your input!

yes, this is a known issue (in Debian's arm64 toolchain): https://bugzilla.proxmox.com/show_bug.cgi?id=7941 https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/349

This forum (except for the sections explicitly marked as German) are in English only, please translate before posting!

this was actually CVE-2026-99999 aka "PwnEscape", and is fixed in proxmox-kernel-7.0.14-24-pve

the fix is included in proxmox-kernel-7.0.14-24-pve(-signed), which is currently available up to the pve-no-subscription repository and will hit enterprise soon. the 7.0.14 series is the only currently supported kernel series, there won't be updates for EOL kernel series or product releaess.

because of the `/`, you need to pass the poolid as parameter, not as part of the path: pvesh get /pools --poolid Pool_Level1/Pool_Level2 should work.

if you do not require vhost, then you can disable it on the host level (by preventing the corresponding module from being loaded and unloading it). but PVE 8 is EOL, like previously mentioned in this thread, this is just one of many issues affecting it..

https://bugzilla.proxmox.com/show_bug.cgi?id=4244 contains some related discussion

the fix was applied in git, but the package pve-container hasn't seen a bump since then.

it contains a few other fixes in other parts of the kernel as well, but neither kernel is on enterprise yet.

-22 contains the initial version, -23 contains an updated one

yes ;)

1. please try with the most recent kernel version 2. provide pversion -v 3. provide the VM configs