Recent content by TheMrg

Is escape from unprivileged LXC container is possible? If yes, may mitigate with seccomp?

we have the same question. if we have no VM with CPU type "host", a root user on the VM can not escape?

Aus einen non privileged LXC Container sollte doch diese Lücke nicht ausnutzbar sein, um die Keys oder shadow des Hosts zu lesen. Oder ist es dennoch möglich? Danke.

Thanks. We hope mlx5 is the only one. because we have one Proxmox VE we can not reboot yet.

is proxmox is affacted? we have KVM VMs on it. many thanks

Sehen wir auch so. Der user hat ja keine möglichkeit eine qcow2 zu laden (zb als disk) in seine VM um so auf dem Host Daten lesen/schreiben zu können über die Lücke Danke soweit.

ist proxmox betroffen? https://access.redhat.com/security/cve/cve-2024-4467 welche auswirkungen hat dies? kann dies AUS einem Container (LXC) oder einer VM heraus genutzt werden? oder von einem User per GUI (user hat nur PVEVMUser permissions)? danke.

many thanks. 50% is a lot. we have other proxmox nodes with 80% memory consumtion, without problems.

we have the same issue on 3 proxmox nodes. all 3 nodes have high RAM consumtion (95% or more). suddenly on each of 3 nodes the VM with most memory was killed due OOM whenever it happens it is time 00:25 Is there a ZFS scrub or so? this happens nearly every month and only on high RAM usage...

Thanks. No we only use Proxmox GUI to set VMs.

Is the CVE-2023-40360 a problem to Proxmox? Proxmox using KVM for virtual machines. Many thanks.

we are unclear about inception. we use zen2 AMD cpu. are we safe? https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7005.html is unclear and "These architectures do not require a microcode update since the IBPB feature introduced in 2018 to mitigate Spectre v2 already works fine...

any news? safe to upgrade ?

today new microcode was published for buster. now we are on 0xfa and happy

Thanks, yes we are on 3.2-5 all 3 fixes?