From:
  * https://bugzilla.suse.com/show_bug.cgi?id=1209554
  * https://bugzilla.suse.com/show_bug.cgi?id=1218484
  * https://bugzilla.suse.com/show_bug.cgi?id=1220062
  * https://bugzilla.suse.com/show_bug.cgi?id=1220065
  * https://bugzilla.suse.com/show_bug.cgi?id=1220134
and looking for githup or patch references URLs, trying to pin down the patches is not easy. Here are most, I think:
https://github.com/qemu/qemu/commit/77668e4b9bca03a856c27ba899a2513ddf52bb52
https://github.com/qemu/qemu/commit/2220e8189fb94068dbad333228659fbac819abb0
https://lore.kernel.org/all/20240213055345-mutt-send-email-mst%40kernel.org/
https://github.com/qemu/qemu/commit/77668e4b9bca03a856c27ba899a2513ddf52bb52
but it needs careful checking. One at least looks to be missing.

Assigning to Giuseppe who put up the current version.

Assignee: bugsquad => ghibomgx

SUSE has issued an advisory on April 23:
https://lwn.net/Articles/970884/

According to Debian:
  - CVE-2023-6683 is fixed by: https://gitlab.com/qemu-project/qemu/-/commit/405484b29f6548c7b86549b0f961b906337aa68a
  - CVE-2024-3446 is fixed by: https://patchew.org/QEMU/20240409105537.18308-1-philmd@linaro.org/
  - CVE-2024-3447 is fixed by: https://patchew.org/QEMU/20240404085549.16987-1-philmd@linaro.org/ and https://patchew.org/QEMU/20240409145524.27913-1-philmd@linaro.org/

CVE: CVE-2023-1544, CVE-2023-6693, CVE-2024-24474, CVE-2024-26327, CVE-2024-26328 => CVE-2023-1544, CVE-2023-6683, CVE-2023-6693, CVE-2024-24474, CVE-2024-26327, CVE-2024-26328, CVE-2024-3446, CVE-2024-3447
Summary: qemu new security issues CVE-2023-1544, CVE-2023-6693, CVE-2024-24474, CVE-2024-2632[78] => qemu new security issues CVE-2023-1544, CVE-2023-6683, CVE-2023-6693, CVE-2024-24474, CVE-2024-2632[78], CVE-2024-344[67]

RedHat has issued an advisory on April 30:
https://lwn.net/Articles/971720/

Status comment: Patches available from openSUSE => Patches available from openSUSE and Redhat
Summary: qemu new security issues CVE-2023-1544, CVE-2023-6683, CVE-2023-6693, CVE-2024-24474, CVE-2024-2632[78], CVE-2024-344[67] => qemu new security issues CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-2632[78], CVE-2024-344[67]
CVE: CVE-2023-1544, CVE-2023-6683, CVE-2023-6693, CVE-2024-24474, CVE-2024-26327, CVE-2024-26328, CVE-2024-3446, CVE-2024-3447 => CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-26327, CVE-2024-26328, CVE-2024-3446, CVE-2024-3447

For cauldron, there is version qemu-9.0.1-1.mga10 which is the latest stable upstream. For mga9 there is version qemu-7.2.12-2.mga9 in core/updates_testing, which is the latest of 7.2.x series and should address all the issues (however I've not checked them one by one).

Version: Cauldron => 9

openSUSE has issued an advisory on August 20:
https://lists.suse.com/pipermail/sle-updates/2024-August/036644.html

Summary: qemu new security issues CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-2632[78], CVE-2024-344[67] => qemu new security issues CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-2632[78], CVE-2024-344[67], CVE-2024-4467, CVE-2024-7409
CVE: CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-26327, CVE-2024-26328, CVE-2024-3446, CVE-2024-3447 => CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-26327, CVE-2024-26328, CVE-2024-3446, CVE-2024-3447, CVE-2024-4467, CVE-2024-7409

There is qemu-7.2.14-1.mga9 in updates_testing which should add all the known fixes.

openSUSE has issued an advisory on November 28:
https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/HL7L7OSCUZ44UAQCOB6IUOFBWKV6ECP2/

Summary: qemu new security issues CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-2632[78], CVE-2024-344[67], CVE-2024-4467, CVE-2024-7409 => qemu new security issues CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-2632[78], CVE-2024-344[67], CVE-2024-4467, CVE-2024-7409, CVE-2024-8354, CVE-2024-8612
CVE: CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-26327, CVE-2024-26328, CVE-2024-3446, CVE-2024-3447, CVE-2024-4467, CVE-2024-7409 => CVE-2023-1544, CVE-2023-3019, CVE-2023-3255, CVE-2023-5088, CVE-2023-6683, CVE-2023-6693, CVE-2023-42467, CVE-2024-24474, CVE-2024-26327, CVE-2024-26328, CVE-2024-3446, CVE-2024-3447, CVE-2024-4467, CVE-2024-7409, CVE-2024-8354, CVE-2024-8612

There is qemu-7.2.15-1.mga9 in updates_testing which should include all the fixes merged upstream (though the package still doesn't address completely bug #32895).

Suggested advisory:
========================

The updated packages fix security vulnerabilities:

A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device. This flaw allows a crafted guest driver to allocate and initialize a huge number of page tables to be used as a ring of descriptors for CQ and async events, potentially leading to an out-of-bounds read and crash of QEMU. (CVE-2023-1544)

A DMA reentrancy issue leading to a use-after-free error was found in the e1000e NIC emulation code in QEMU. This issue could allow a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. (CVE-2023-3019)

A flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. A wrong exit condition may lead to an infinite loop when inflating an attacker controlled zlib buffer in the `inflate_buffer` function. This could allow a remote authenticated client who is able to send a clipboard to the VNC server to trigger a denial of service. (CVE-2023-3255)

A bug in QEMU could cause a guest I/O operation otherwise addressed to an arbitrary disk offset to be targeted to offset 0 instead (potentially overwriting the VM's boot code). This could be used, for example, by L2 guests with a virtual disk (vdiskL2) stored on a virtual disk of an L1 (vdiskL1) hypervisor to read and/or write data to LBA 0 of vdiskL1, potentially gaining control of L1 at its next reboot. (CVE-2023-5088)

A flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. The qemu_clipboard_request() function can be reached before vnc_server_cut_text_caps() was called and had the chance to initialize the clipboard peer, leading to a NULL pointer dereference. This could allow a malicious authenticated VNC client to crash QEMU and trigger a denial of service. (CVE-2023-6683)

A stack based buffer overflow was found in the virtio-net device of QEMU. This issue occurs when flushing TX in the virtio_net_flush_tx function if guest features VIRTIO_NET_F_HASH_REPORT, VIRTIO_F_VERSION_1 and VIRTIO_NET_F_MRG_RXBUF are enabled. This could allow a malicious user to overwrite local variables allocated on the stack. Specifically, the `out_sg` variable could be used to read a part of process memory and send it to the wire, causing an information leak. (CVE-2023-6693)

QEMU through 8.0.0 could trigger a division by zero in scsi_disk_reset in hw/scsi/scsi-disk.c because scsi_disk_emulate_mode_select does not prevent s->qdev.blocksize from being 256. This stops QEMU and the guest immediately. (CVE-2023-42467)

QEMU before 8.2.0 has an integer underflow, and resultant buffer overflow, via a TI command when an expected non-DMA transfer length is less than the length of the available FIFO data. This occurs in esp_do_nodma in hw/scsi/esp.c because of an underflow of async_len. (CVE-2024-24474)

An issue was discovered in QEMU 7.1.0 through 8.2.1. register_vfs in hw/pci/pcie_sriov.c mishandles the situation where a guest writes NumVFs greater than TotalVFs, leading to a buffer overflow in VF implementations. (CVE-2024-26327)

An issue was discovered in QEMU 7.1.0 through 8.2.1. register_vfs in hw/pci/pcie_sriov.c does not set NumVFs to PCI_SRIOV_TOTAL_VF, and thus interaction with hw/nvme/ctrl.c is mishandled. (CVE-2024-26328)

A double free vulnerability was found in QEMU virtio devices (virtio-gpu, virtio-serial-bus, virtio-crypto), where the mem_reentrancy_guard flag insufficiently protects against DMA reentrancy issues. This issue could allow a malicious privileged guest user to crash the QEMU process on the host, resulting in a denial of service or allow arbitrary code execution within the context of the QEMU process on the host. (CVE-2024-3446)

A heap-based buffer overflow was found in the SDHCI device emulation of QEMU. The bug is triggered when both `s->data_count` and the size of `s->fifo_buffer` are set to 0x200, leading to an out-of-bound access. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. (CVE-2024-3447)

A flaw was found in the QEMU disk image utility (qemu-img) 'info' command. A specially crafted image file containing a `json:{}` value describing block devices in QMP could cause the qemu-img process on the host to consume large amounts of memory or CPU time, leading to denial of service or read/write to an existing external file. (CVE-2024-4467)

A flaw was found in the QEMU NBD Server. This vulnerability allows a denial of service (DoS) attack via improper synchronization during socket closure when a client keeps a socket open as the server is taken offline. (CVE-2024-7409)

A flaw was found in QEMU. An assertion failure was present in the usb_ep_get() function in hw/net/core.c when trying to get the USB endpoint from a USB device. This flaw may allow a malicious unprivileged guest user to crash the QEMU process on the host and cause a denial of service condition. (CVE-2024-8354)

A flaw was found in QEMU, in the virtio-scsi, virtio-blk, and virtio-crypto devices. The size for virtqueue_push as set in virtio_scsi_complete_req / virtio_blk_req_complete / virito_crypto_req_complete could be larger than the true size of the data which has been sent to guest. Once virtqueue_push() finally calls dma_memory_unmap to ummap the in_iov, it may call the address_space_write function to write back the data. Some uninitialized data may exist in the bounce.buffer, leading to an information leak. (CVE-2024-8612)

References:
https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/ES5DXAAMYUC767MUW4BPRP6ZPDL6SUW6/
https://lists.suse.com/pipermail/sle-updates/2024-April/035064.html
https://lwn.net/Articles/971720/
https://lists.suse.com/pipermail/sle-updates/2024-August/036644.html
https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/HL7L7OSCUZ44UAQCOB6IUOFBWKV6ECP2/
========================

Updated packages in core/updates_testing:
========================
qemu-7.2.15-1.mga9
qemu-audio-alsa-7.2.15-1.mga9
qemu-audio-dbus-7.2.15-1.mga9
qemu-audio-jack-7.2.15-1.mga9
qemu-audio-oss-7.2.15-1.mga9
qemu-audio-pa-7.2.15-1.mga9
qemu-audio-sdl-7.2.15-1.mga9
qemu-audio-spice-7.2.15-1.mga9
qemu-block-curl-7.2.15-1.mga9
qemu-block-dmg-7.2.15-1.mga9
qemu-block-iscsi-7.2.15-1.mga9
qemu-block-nfs-7.2.15-1.mga9
qemu-block-rbd-7.2.15-1.mga9
qemu-block-ssh-7.2.15-1.mga9
qemu-char-baum-7.2.15-1.mga9
qemu-char-spice-7.2.15-1.mga9
qemu-common-7.2.15-1.mga9
qemu-device-display-qxl-7.2.15-1.mga9
qemu-device-display-vhost-user-gpu-7.2.15-1.mga9
qemu-device-display-virtio-gpu-7.2.15-1.mga9
qemu-device-display-virtio-gpu-ccw-7.2.15-1.mga9
qemu-device-display-virtio-gpu-gl-7.2.15-1.mga9
qemu-device-display-virtio-gpu-pci-7.2.15-1.mga9
qemu-device-display-virtio-gpu-pci-gl-7.2.15-1.mga9
qemu-device-display-virtio-vga-7.2.15-1.mga9
qemu-device-display-virtio-vga-gl-7.2.15-1.mga9
qemu-device-usb-host-7.2.15-1.mga9
qemu-device-usb-redirect-7.2.15-1.mga9
qemu-device-usb-smartcard-7.2.15-1.mga9
qemu-docs-7.2.15-1.mga9
qemu-guest-agent-7.2.15-1.mga9
qemu-img-7.2.15-1.mga9
qemu-kvm-7.2.15-1.mga9
qemu-kvm-core-7.2.15-1.mga9
qemu-pr-helper-7.2.15-1.mga9
qemu-system-aarch64-7.2.15-1.mga9
qemu-system-aarch64-core-7.2.15-1.mga9
qemu-system-alpha-7.2.15-1.mga9
qemu-system-alpha-core-7.2.15-1.mga9
qemu-system-arm-7.2.15-1.mga9
qemu-system-arm-core-7.2.15-1.mga9
qemu-system-avr-7.2.15-1.mga9
qemu-system-avr-core-7.2.15-1.mga9
qemu-system-cris-7.2.15-1.mga9
qemu-system-cris-core-7.2.15-1.mga9
qemu-system-hppa-7.2.15-1.mga9
qemu-system-hppa-core-7.2.15-1.mga9
qemu-system-loongarch64-7.2.15-1.mga9
qemu-system-loongarch64-core-7.2.15-1.mga9
qemu-system-m68k-7.2.15-1.mga9
qemu-system-m68k-core-7.2.15-1.mga9
qemu-system-microblaze-7.2.15-1.mga9
qemu-system-microblaze-core-7.2.15-1.mga9
qemu-system-mips-7.2.15-1.mga9
qemu-system-mips-core-7.2.15-1.mga9
qemu-system-nios2-7.2.15-1.mga9
qemu-system-nios2-core-7.2.15-1.mga9
qemu-system-or1k-7.2.15-1.mga9
qemu-system-or1k-core-7.2.15-1.mga9
qemu-system-ppc-7.2.15-1.mga9
qemu-system-ppc-core-7.2.15-1.mga9
qemu-system-riscv-7.2.15-1.mga9
qemu-system-riscv-core-7.2.15-1.mga9
qemu-system-rx-7.2.15-1.mga9
qemu-system-rx-core-7.2.15-1.mga9
qemu-system-s390x-7.2.15-1.mga9
qemu-system-s390x-core-7.2.15-1.mga9
qemu-system-sh4-7.2.15-1.mga9
qemu-system-sh4-core-7.2.15-1.mga9
qemu-system-sparc-7.2.15-1.mga9
qemu-system-sparc-core-7.2.15-1.mga9
qemu-system-tricore-7.2.15-1.mga9
qemu-system-tricore-core-7.2.15-1.mga9
qemu-system-x86-7.2.15-1.mga9
qemu-system-x86-core-7.2.15-1.mga9
qemu-system-xtensa-7.2.15-1.mga9
qemu-system-xtensa-core-7.2.15-1.mga9
qemu-tests-7.2.15-1.mga9
qemu-tools-7.2.15-1.mga9
qemu-ui-curses-7.2.15-1.mga9
qemu-ui-dbus-7.2.15-1.mga9
qemu-ui-egl-headless-7.2.15-1.mga9
qemu-ui-gtk-7.2.15-1.mga9
qemu-ui-opengl-7.2.15-1.mga9
qemu-ui-sdl-7.2.15-1.mga9
qemu-ui-spice-app-7.2.15-1.mga9
qemu-ui-spice-core-7.2.15-1.mga9
qemu-user-7.2.15-1.mga9
qemu-user-binfmt-7.2.15-1.mga9
qemu-user-static-7.2.15-1.mga9
qemu-user-static-aarch64-7.2.15-1.mga9
qemu-user-static-alpha-7.2.15-1.mga9
qemu-user-static-arm-7.2.15-1.mga9
qemu-user-static-cris-7.2.15-1.mga9
qemu-user-static-hexagon-7.2.15-1.mga9
qemu-user-static-hppa-7.2.15-1.mga9
qemu-user-static-loongarch64-7.2.15-1.mga9
qemu-user-static-m68k-7.2.15-1.mga9
qemu-user-static-microblaze-7.2.15-1.mga9
qemu-user-static-mips-7.2.15-1.mga9
qemu-user-static-nios2-7.2.15-1.mga9
qemu-user-static-or1k-7.2.15-1.mga9
qemu-user-static-ppc-7.2.15-1.mga9
qemu-user-static-riscv-7.2.15-1.mga9
qemu-user-static-s390x-7.2.15-1.mga9
qemu-user-static-sh4-7.2.15-1.mga9
qemu-user-static-sparc-7.2.15-1.mga9
qemu-user-static-x86-7.2.15-1.mga9
qemu-user-static-xtensa-7.2.15-1.mga9
qemu-virtiofsd-7.2.15-1.mga9

from SRPM:
qemu-7.2.15-1.mga9.src.rpm

Assignee: ghibomgx => qa-bugs
Whiteboard: MGA9TOO => (none)
Status: NEW => ASSIGNED
Status comment: Patches available from openSUSE and Redhat => (none)

MGA9-64 Plasma Wayland on Compaq H000SB
No installation issues.
Checked bug 32332, but found not info that I can understand to setup such beast.
Found https://www.qemu.org/docs/master/system/introduction.html and copy/paste the commands shown there, but at the end I get:
$ qemu-system-aarch64 \ -machine type=virt,virtualization=on,pflash0=rom,pflash1=efivars \ -m 4096 \
> -cpu max,pauth-impdef=on \
-smp 4 \
-accel tcg \
> -device virtio-net-pci,netdev=unet \
-device virtio-scsi-pci \
-device scsi-hd,drive=hd \
> -netdev user,id=unet,hostfwd=tcp::2222-:22 \
> -blockdev driver=raw,node-name=hd,file.driver=host_device,file.filename=/dev/sdq5 \> -serial mon:stdio \
-display none \
> -blockdev node-name=rom,driver=file,filename=/home/tester9/pc-bios/edk2-aarch64-code.fd,read-only=true \
-blockdev node-name=efivars,driver=file,filename=$HOME/images/qemu-arm64-efivars
qemu-system-aarch64: No machine specified, and there is no default
Use -machine help to list supported machines

Giving up here, leave for higher intelligences on the matter.

CC: (none) => herman.viaene

Created attachment 14795 [details]
Log of update qemu

Updated without issues
gnome-boxes run the VM, I update the system in VM and reboot without issues, can use the usb attached in the real hardware memory in the VM

I have an issue build with mock for aarch64 but need to test with the previous packages

(In reply to katnatek from comment #11)
> Created attachment 14795 [details]
> Log of update qemu
> 
> Updated without issues
> gnome-boxes run the VM, I update the system in VM and reboot without issues,
> can use the usb attached in the real hardware memory in the VM
> 
> I have an issue build with mock for aarch64 but need to test with the
> previous packages

The issue persist with the current packages, then is something to report to devs and not related to this update

The system needs reboot to all qemu features that use mock, works as must
Perhaps add a warning like in kernel, glibc and similar would be good

Installed and tested without issues.


Host system: Mageia 9, x86_64, AMD Ryzen 5 5600G with Radeon Graphics using amdgpu driver.


Tested:
- QEMU/KVM x86_64;
- QEMU aarch64 emulation;
- virsh;
- virt-manager;
- virt-viewer;
- start, stop, pause;
- QXL/SPICE display;
- "Radeon RX 6500 XT" GPU PCI pass through to Mageia 9 guest (using amdgpu driver) and Windows 10 guest;
- USB pass through;
- host directory mount in GNU/Linux guests;
- virtio driver in GNU/Linux and Windows guests;
- integration with libvirt and machinectl
- shared clipboard
- desktop resizing


Tested Guests:
- Android x86 9 x86_64
- FreeBSD 14 x86_64
- Kail Linux x86_64
- Mageia 9 x86_64
- Mageia 9 aarch64
- Mageia Cauldron x86_64
- memtest86
- Tails 6 x86_64
- Windows 10
- Windows 11



$ uname -a
Linux jupiter 6.6.61-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Thu Nov 14 15:07:14 UTC 2024 x86_64 GNU/Linux
$ rpm -qa | grep -P '^qemu-.*7\.2\.15' | sort
qemu-audio-alsa-7.2.15-1.mga9
qemu-audio-dbus-7.2.15-1.mga9
qemu-audio-jack-7.2.15-1.mga9
qemu-audio-oss-7.2.15-1.mga9
qemu-audio-pa-7.2.15-1.mga9
qemu-audio-sdl-7.2.15-1.mga9
qemu-audio-spice-7.2.15-1.mga9
qemu-block-curl-7.2.15-1.mga9
qemu-block-dmg-7.2.15-1.mga9
qemu-block-iscsi-7.2.15-1.mga9
qemu-block-nfs-7.2.15-1.mga9
qemu-block-rbd-7.2.15-1.mga9
qemu-block-ssh-7.2.15-1.mga9
qemu-char-baum-7.2.15-1.mga9
qemu-char-spice-7.2.15-1.mga9
qemu-common-7.2.15-1.mga9
qemu-device-display-qxl-7.2.15-1.mga9
qemu-device-display-vhost-user-gpu-7.2.15-1.mga9
qemu-device-display-virtio-gpu-7.2.15-1.mga9
qemu-device-display-virtio-gpu-ccw-7.2.15-1.mga9
qemu-device-display-virtio-gpu-gl-7.2.15-1.mga9
qemu-device-display-virtio-gpu-pci-7.2.15-1.mga9
qemu-device-display-virtio-gpu-pci-gl-7.2.15-1.mga9
qemu-device-display-virtio-vga-7.2.15-1.mga9
qemu-device-display-virtio-vga-gl-7.2.15-1.mga9
qemu-device-usb-host-7.2.15-1.mga9
qemu-device-usb-redirect-7.2.15-1.mga9
qemu-device-usb-smartcard-7.2.15-1.mga9
qemu-img-7.2.15-1.mga9
qemu-kvm-7.2.15-1.mga9
qemu-pr-helper-7.2.15-1.mga9
qemu-system-aarch64-7.2.15-1.mga9
qemu-system-aarch64-core-7.2.15-1.mga9
qemu-system-x86-7.2.15-1.mga9
qemu-system-x86-core-7.2.15-1.mga9
qemu-ui-curses-7.2.15-1.mga9
qemu-ui-egl-headless-7.2.15-1.mga9
qemu-ui-gtk-7.2.15-1.mga9
qemu-ui-opengl-7.2.15-1.mga9
qemu-ui-sdl-7.2.15-1.mga9
qemu-ui-spice-app-7.2.15-1.mga9
qemu-ui-spice-core-7.2.15-1.mga9
qemu-user-static-aarch64-7.2.15-1.mga9
qemu-virtiofsd-7.2.15-1.mga9
$ systemctl status libvirtd.service
● libvirtd.service - Virtualization daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-12-03 00:24:19 WET; 48min ago
TriggeredBy: ● libvirtd.socket
             ● libvirtd-ro.socket
             ● libvirtd-admin.socket
       Docs: man:libvirtd(8)
             https://libvirt.org
   Main PID: 72078 (libvirtd)
      Tasks: 20 (limit: 32768)
     Memory: 45.3M
        CPU: 3.022s
     CGroup: /system.slice/libvirtd.service
             └─72078 /usr/sbin/libvirtd --timeout 120

CC: (none) => mageia

Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2024-0387.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED