Subject: PSA-2026-00029-1: overflow in ipv6 fragmentation code
Advisory date: 2026-07-20
Packages: proxmox-kernel-*
Details:
An in-slab linear overflow issue was discovered in the Linux kernel's IPv6 fragementation code. This issue could be...
Subject: PSA-2026-00028-1: "IonStack"/"GhostLock" use after free vulnerability in the Linux kernel
Advisory date: 2026-07-20
Packages: proxmox-kernel-*
Details:
A Use-After-Free issue in the kernel's rtmutex/futex-PI code allows an attacker...
Hi, new here and didn't find this thread before posting my own. ( https://forum.proxmox.com/threads/lets-talk-deduplication-and-immutability.182803/ )
But id like to explain how I have managed to use AWS S3 with Object lock to achieve immutable...
Maybe the the IO-Wait gets so high that corosync drops out or the Watchdog gets triggered?
You could try to set a bandwidth limit in the backup job or a fleecing storage?
Hello,
Thank you for your response. Is the version now available?
Thanks again, @j.theisen, for the quick diagnosis you provided via the ticket.
I won’t hide the fact that I had to switch to prioritizing the entire VLAN via TC and disable the...
Thanks, this is very useful. As we developed for clouds until now, we did not need a local lab. It is difficult to build one since we do not own a datacenter but I would like to rent some lab where I can test and debug our integration with...
Thank you for your insights!
That's a very good point regarding the possibility that the I/O error could be occurring at the QEMU layer rather than in the FC, multipath, or LVM stack.
I also agree that moving the backup window to Saturday would...
Maybe the the IO-Wait gets so high that corosync drops out or the Watchdog gets triggered?
You could try to set a bandwidth limit in the backup job or a fleecing storage?
Thank you for your suggestion!
That's a good point. I'll check with our backup team to see whether it's possible to move one of the affected VMs to a different backup day so we can observe whether the issue still occurs. I'll gather more...
I am not familiar with how Bacula integrates with PVE. If it operates through the QEMU layer, similar to PBS and Veeam, it is possible that the I/O error originates at a higher layer than FC, multipath, or LVM - that is, within the QEMU layer...
My first thought was if there's backup running during that time, and I kept on reading until spotting it:
"Our backup infrastructure uses Bacula, and backups are executed on Fridays, so I'm wondering if increased I/O load could somehow expose an...
Maybe the the IO-Wait gets so high that corosync drops out or the Watchdog gets triggered?
You could try to set a bandwidth limit in the backup job or a fleecing storage?
Sie haben zwei Möglichkeiten:
Die erste Möglichkeit ist die schrittweise Aktualisierung Ihres Systems:
- Aktualisieren Sie Ihr System auf Proxmox 6.4:
apt update && apt full upgrade
- Aktualisieren Sie Proxmox 6 auf 7...
Most likely this is some typo or an erroneous pasting during editing fstab.
As this path doesn't exist, just comment out this line in fstab.
Then run an update as usual and verify that the warnings are gone :).
Today we're introducing a dedicated repository for debug symbol packages, reachable at https://dbgsym.proxmox.com/.
Debug symbol packages (named <package>-dbgsym) contain the detached debug information for their matching binary package. They are...
I'm trying to delete a template, and it returns the error:
My typical method for finding linked clones using a template's storage is to run:
grep -r base-100 /etc/pve/nodes/*/qemu-server
However in this case that returns only the template...
Sie haben zwei Möglichkeiten:
Die erste Möglichkeit ist die schrittweise Aktualisierung Ihres Systems:
- Aktualisieren Sie Ihr System auf Proxmox 6.4:
apt update && apt full upgrade
- Aktualisieren Sie Proxmox 6 auf 7...