| ▲ | Flockster 3 hours ago | |
Going by the proxmox forum the fix is already in the sources (proxmox released their kernel based on them a few days ago). But I could not see, if it is already released for the users. https://forum.proxmox.com/threads/cve-2026-98432-in-proxmox-... | ||
| ▲ | tlamponi 3 hours ago | parent [-] | |
Yes, we (Proxmox) included the fix for this in 7.0.14-25, which was initially packaged two weeks ago. It went through internal QA and to the test soon after that, then a few days later to the no-subscription repository and as of yesterday morning CET it was cleared for the enterprise one, so it's available on all repos of all Products we got in their current supported releases. For kernel updates we where even more conservative in the past, but with the current churn on often quite relevant fixes picked up the pace a bit on moving them along, trying still to balance rolling out fixes fast(er) while not doing that so fast that tricky (hardware/setup specific) regressions don't get caught. edit: As this makes the rounds we also released a PSA for it now [0] to make our status here easier to find. [0]: https://forum.proxmox.com/threads/proxmox-virtual-environmen... | ||