CVE-2023-0330

You can check your qemu version on the pve summary page. Mine is "qemu-server: 7.3-4". Or
Code:
dpkg -l |grep qemu
.
 
Hi,
yes, using a different SCSI controller should mitigate the issue.

The qemu-server version is not relevant here, it's the pve-qemu-kvm package.

FYI, a fix is already included in pve-qemu-kvm=7.2.0-7 currently available on the no-subscription repository. Here is the relevant commit. The patch added there states
which is the same issue referenced in the mail that's linked in the CVE. I also tried to run the reproducer from there, and with pve-qemu-kvm=7.2.0-7 it doesn't produce any errors while with upstream/stock QEMU 7.2 it results in a segfault.
 
Hi,
yes, using a different SCSI controller should mitigate the issue.

The qemu-server version is not relevant here, it's the pve-qemu-kvm package.

FYI, a fix is already included in pve-qemu-kvm=7.2.0-7 currently available on the no-subscription repository. Here is the relevant commit. The patch added there states

which is the same issue referenced in the mail that's linked in the CVE. I also tried to run the reproducer from there, and with pve-qemu-kvm=7.2.0-7 it doesn't produce any errors while with upstream/stock QEMU 7.2 it results in a segfault.
Thank you very much!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!