qemu - Debian Package Tracker

general

source: qemu (main)
version: 1:11.0.3+ds-2
maintainer: Debian QEMU Team (archive) (DMD)
uploaders: Michael Tokarev [DMD]
arch: all
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1:5.2+dfsg-11+deb11u3
o-o-sec: 1:5.2+dfsg-11+deb11u5
oldstable: 1:7.2+dfsg-7+deb12u18
old-sec: 1:7.2+dfsg-7+deb12u15
old-bpo: 1:10.0.2+ds-2+deb13u1~bpo12+1
stable: 1:10.0.11+ds-0+deb13u1
stable-sec: 1:10.0.2+ds-2+deb13u1
stable-bpo: 1:11.0.2+ds-2~bpo13+1
testing: 1:11.0.2+ds-2
unstable: 1:11.0.3+ds-2
exp: 1:11.1.0~rc1+ds-1

versioned links

1:5.2+dfsg-11+deb11u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:5.2+dfsg-11+deb11u5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:7.2+dfsg-7+deb12u15: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:7.2+dfsg-7+deb12u18: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:10.0.2+ds-2+deb13u1~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:10.0.2+ds-2+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:10.0.11+ds-0+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:10.2.2+ds-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:11.0.2+ds-2~bpo13+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:11.0.2+ds-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:11.0.3+ds-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:11.0.3+ds-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:11.1.0~rc1+ds-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

qemu-block-extra
qemu-guest-agent (1 bugs: 0, 0, 1, 0)
qemu-system (6 bugs: 0, 2, 4, 0)
qemu-system-arm (3 bugs: 0, 1, 2, 0)
qemu-system-common (5 bugs: 0, 0, 5, 0)
qemu-system-data (1 bugs: 0, 0, 1, 0)
qemu-system-gui (2 bugs: 0, 2, 0, 0)
qemu-system-mips
qemu-system-misc
qemu-system-modules-opengl
qemu-system-modules-spice
qemu-system-ppc (3 bugs: 0, 3, 0, 0)
qemu-system-riscv (1 bugs: 0, 1, 0, 0)
qemu-system-s390x
qemu-system-sparc
qemu-system-x86 (20 bugs: 0, 15, 5, 0)
qemu-system-xen
qemu-user (4 bugs: 0, 3, 1, 0)
qemu-user-binfmt (1 bugs: 0, 1, 0, 0)
qemu-utils (1 bugs: 0, 1, 0, 0)

action needed

11 security issues in trixie high

There are 11 open security issues in trixie.

1 important issue:

CVE-2026-12080: A flaw was found in the QEMU Guest Agent (qga). A local unprivileged user can exploit a vulnerability in the guest-ssh-add-authorized-keys command handler by manipulating symbolic links. This can occur either through a deterministic directory-symlink bypass or a Time-of-Check to Time-of-Use (TOCTOU) file-symlink race. Successful exploitation allows the attacker to gain ownership of arbitrary root-owned files or directories, leading to root access. This vulnerability requires an external management layer (e.g., libvirt) to trigger the affected code path.

10 issues left for the package maintainer to handle:

CVE-2021-3735: (postponed; to be fixed through a stable update) A deadlock issue was found in the AHCI controller device of QEMU. It occurs on a software reset (ahci_reset_port) while handling a host-to-device Register FIS (Frame Information Structure) packet from the guest. A privileged user inside the guest could use this flaw to hang the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability.
CVE-2022-3872: (postponed; to be fixed through a stable update) An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.
CVE-2023-1386: (postponed; to be fixed through a stable update) A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. When a local user in the guest writes an executable file with SUID or SGID, none of these privileged bits are correctly dropped. As a result, in rare circumstances, this flaw could be used by malicious users in the guest to elevate their privileges within the guest and help a host local user to elevate privileges on the host.
CVE-2024-8354: (needs triaging) 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-8612: (needs triaging) 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-2019-12067: (postponed; to be fixed through a stable update) The ahci_commit_buf function in ide/ahci.c in QEMU allows attackers to cause a denial of service (NULL dereference) when the command header 'ad->cur_cmd' is null.
CVE-2020-25741: (postponed; to be fixed through a stable update) fdctrl_write_data in hw/block/fdc.c in QEMU 5.0.0 has a NULL pointer dereference via a NULL block pointer for the current drive.
CVE-2020-25742: (postponed; to be fixed through a stable update) pci_change_irq_level in hw/pci/pci.c in QEMU before 5.1.1 has a NULL pointer dereference because pci_get_bus() might not return a valid pointer.
CVE-2020-25743: (postponed; to be fixed through a stable update) hw/ide/pci.c in QEMU before 5.1.1 can trigger a NULL pointer dereference because it lacks a pointer check before an ide_cancel_dma_sync call.
CVE-2020-35503: (postponed; to be fixed through a stable update) A NULL pointer dereference flaw was found in the megasas-gen2 SCSI host bus adapter emulation of QEMU in versions before and including 6.0. This issue occurs in the megasas_command_cancelled() callback function while dropping a SCSI request. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.

You can find information about how to handle these issues in the security team's documentation.

8 issues that should be fixed with the next stable update:

CVE-2026-8348:
CVE-2026-9238:
CVE-2026-15578:
CVE-2026-15705:
CVE-2026-16043:
CVE-2026-48002:
CVE-2026-61475:
CVE-2026-63319:

Created: 2023-06-11 Last update: 2026-07-27 10:31

10 security issues in sid high

There are 10 open security issues in sid.

10 important issues:

CVE-2021-3735: A deadlock issue was found in the AHCI controller device of QEMU. It occurs on a software reset (ahci_reset_port) while handling a host-to-device Register FIS (Frame Information Structure) packet from the guest. A privileged user inside the guest could use this flaw to hang the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability.
CVE-2022-3872: An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.
CVE-2023-1386: A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. When a local user in the guest writes an executable file with SUID or SGID, none of these privileged bits are correctly dropped. As a result, in rare circumstances, this flaw could be used by malicious users in the guest to elevate their privileges within the guest and help a host local user to elevate privileges on the host.
CVE-2024-8612: 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-2019-12067: The ahci_commit_buf function in ide/ahci.c in QEMU allows attackers to cause a denial of service (NULL dereference) when the command header 'ad->cur_cmd' is null.
CVE-2020-25741: fdctrl_write_data in hw/block/fdc.c in QEMU 5.0.0 has a NULL pointer dereference via a NULL block pointer for the current drive.
CVE-2020-25742: pci_change_irq_level in hw/pci/pci.c in QEMU before 5.1.1 has a NULL pointer dereference because pci_get_bus() might not return a valid pointer.
CVE-2020-25743: hw/ide/pci.c in QEMU before 5.1.1 can trigger a NULL pointer dereference because it lacks a pointer check before an ide_cancel_dma_sync call.
CVE-2020-35503: A NULL pointer dereference flaw was found in the megasas-gen2 SCSI host bus adapter emulation of QEMU in versions before and including 6.0. This issue occurs in the megasas_command_cancelled() callback function while dropping a SCSI request. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
CVE-2026-12080: A flaw was found in the QEMU Guest Agent (qga). A local unprivileged user can exploit a vulnerability in the guest-ssh-add-authorized-keys command handler by manipulating symbolic links. This can occur either through a deterministic directory-symlink bypass or a Time-of-Check to Time-of-Use (TOCTOU) file-symlink race. Successful exploitation allows the attacker to gain ownership of arbitrary root-owned files or directories, leading to root access. This vulnerability requires an external management layer (e.g., libvirt) to trigger the affected code path.

Created: 2022-07-04 Last update: 2026-07-27 10:31

18 security issues in forky high

There are 18 open security issues in forky.

18 important issues:

CVE-2021-3735: A deadlock issue was found in the AHCI controller device of QEMU. It occurs on a software reset (ahci_reset_port) while handling a host-to-device Register FIS (Frame Information Structure) packet from the guest. A privileged user inside the guest could use this flaw to hang the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability.
CVE-2022-3872: An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.
CVE-2023-1386: A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. When a local user in the guest writes an executable file with SUID or SGID, none of these privileged bits are correctly dropped. As a result, in rare circumstances, this flaw could be used by malicious users in the guest to elevate their privileges within the guest and help a host local user to elevate privileges on the host.
CVE-2024-8612: 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-2026-8348:
CVE-2026-9238:
CVE-2019-12067: The ahci_commit_buf function in ide/ahci.c in QEMU allows attackers to cause a denial of service (NULL dereference) when the command header 'ad->cur_cmd' is null.
CVE-2020-25741: fdctrl_write_data in hw/block/fdc.c in QEMU 5.0.0 has a NULL pointer dereference via a NULL block pointer for the current drive.
CVE-2020-25742: pci_change_irq_level in hw/pci/pci.c in QEMU before 5.1.1 has a NULL pointer dereference because pci_get_bus() might not return a valid pointer.
CVE-2020-25743: hw/ide/pci.c in QEMU before 5.1.1 can trigger a NULL pointer dereference because it lacks a pointer check before an ide_cancel_dma_sync call.
CVE-2020-35503: A NULL pointer dereference flaw was found in the megasas-gen2 SCSI host bus adapter emulation of QEMU in versions before and including 6.0. This issue occurs in the megasas_command_cancelled() callback function while dropping a SCSI request. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
CVE-2026-12080: A flaw was found in the QEMU Guest Agent (qga). A local unprivileged user can exploit a vulnerability in the guest-ssh-add-authorized-keys command handler by manipulating symbolic links. This can occur either through a deterministic directory-symlink bypass or a Time-of-Check to Time-of-Use (TOCTOU) file-symlink race. Successful exploitation allows the attacker to gain ownership of arbitrary root-owned files or directories, leading to root access. This vulnerability requires an external management layer (e.g., libvirt) to trigger the affected code path.
CVE-2026-15578:
CVE-2026-15705:
CVE-2026-16043:
CVE-2026-48002:
CVE-2026-61475:
CVE-2026-63319:

Created: 2025-08-09 Last update: 2026-07-27 10:31

43 security issues in bullseye high

There are 43 open security issues in bullseye.

16 important issues:

CVE-2026-3890:
CVE-2026-5763:
CVE-2026-6425:
CVE-2026-8343:
CVE-2026-8348:
CVE-2026-9238:
CVE-2026-12080: A flaw was found in the QEMU Guest Agent (qga). A local unprivileged user can exploit a vulnerability in the guest-ssh-add-authorized-keys command handler by manipulating symbolic links. This can occur either through a deterministic directory-symlink bypass or a Time-of-Check to Time-of-Use (TOCTOU) file-symlink race. Successful exploitation allows the attacker to gain ownership of arbitrary root-owned files or directories, leading to root access. This vulnerability requires an external management layer (e.g., libvirt) to trigger the affected code path.
CVE-2026-15578:
CVE-2026-15705:
CVE-2026-16043:
CVE-2026-48002:
CVE-2026-48003:
CVE-2026-48004:
CVE-2026-48914: A flaw was found in QEMU's virtio-blk device. The issue arises because the device does not properly validate the size of input descriptors before writing data. A malicious guest with high privileges could exploit this vulnerability by submitting a malformed virtio-blk SCSI request, leading to an out-of-bounds write in the host heap memory and a potential denial of service (DoS) for the QEMU process.
CVE-2026-61475:
CVE-2026-63319:

16 issues postponed or untriaged:

CVE-2021-3735: (postponed; to be fixed through a stable update) A deadlock issue was found in the AHCI controller device of QEMU. It occurs on a software reset (ahci_reset_port) while handling a host-to-device Register FIS (Frame Information Structure) packet from the guest. A privileged user inside the guest could use this flaw to hang the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability.
CVE-2022-3872: (postponed; to be fixed through a stable update) An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.
CVE-2023-1386: (postponed; to be fixed through a stable update) A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. When a local user in the guest writes an executable file with SUID or SGID, none of these privileged bits are correctly dropped. As a result, in rare circumstances, this flaw could be used by malicious users in the guest to elevate their privileges within the guest and help a host local user to elevate privileges on the host.
CVE-2024-6505: (postponed; to be fixed through a stable update) A flaw was found in the virtio-net device in QEMU. When enabling the RSS feature on the virtio-net network card, the indirections_table data within RSS becomes controllable. Setting excessively large values may cause an index out-of-bounds issue, potentially resulting in heap overflow access. This flaw allows a privileged user in the guest to crash the QEMU process on the host.
CVE-2024-6519: (postponed; to be fixed through a stable update) A use-after-free vulnerability was found in the QEMU LSI53C895A SCSI Host Bus Adapter emulation. This issue can lead to a crash or VM escape.
CVE-2024-7730: (postponed; to be fixed through a stable update) A heap buffer overflow was found in the virtio-snd device in QEMU. When reading input audio in the virtio-snd input callback, virtio_snd_pcm_in_cb, the function did not check whether the iov can fit the data buffer. This issue can trigger an out-of-bounds write if the size of the virtio queue element is equal to virtio_snd_pcm_status, which makes the available space for audio data zero.
CVE-2024-8354: (postponed; to be fixed through a stable update) 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-8612: (postponed; to be fixed through a stable update) 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-2026-2243: (postponed; to be fixed through a stable update) A flaw was found in QEMU. A specially crafted VMDK image could trigger an out-of-bounds read vulnerability, potentially leading to a 12-byte leak of sensitive information or a denial of service condition (DoS).
CVE-2019-12067: (postponed; to be fixed through a stable update) The ahci_commit_buf function in ide/ahci.c in QEMU allows attackers to cause a denial of service (NULL dereference) when the command header 'ad->cur_cmd' is null.
CVE-2020-25741: (postponed; to be fixed through a stable update) fdctrl_write_data in hw/block/fdc.c in QEMU 5.0.0 has a NULL pointer dereference via a NULL block pointer for the current drive.
CVE-2020-25742: (postponed; to be fixed through a stable update) pci_change_irq_level in hw/pci/pci.c in QEMU before 5.1.1 has a NULL pointer dereference because pci_get_bus() might not return a valid pointer.
CVE-2020-25743: (postponed; to be fixed through a stable update) hw/ide/pci.c in QEMU before 5.1.1 can trigger a NULL pointer dereference because it lacks a pointer check before an ide_cancel_dma_sync call.
CVE-2020-35503: (postponed; to be fixed through a stable update) A NULL pointer dereference flaw was found in the megasas-gen2 SCSI host bus adapter emulation of QEMU in versions before and including 6.0. This issue occurs in the megasas_command_cancelled() callback function while dropping a SCSI request. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
CVE-2021-20255: (postponed; to be fixed through a stable update) A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator of QEMU. This issue occurs while processing controller commands due to a DMA reentry issue. This flaw allows a guest user or process to consume CPU cycles or crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
CVE-2025-11234: (needs triaging) A flaw was found in QEMU. If the QIOChannelWebsock object is freed while it is waiting to complete a handshake, a GSource is leaked. This can lead to the callback firing later on and triggering a use-after-free in the use of the channel. This can be abused by a malicious client with network access to the VNC WebSocket port to cause a denial of service during the WebSocket handshake prior to the VNC client authentication.

11 ignored issues:

CVE-2021-3611: A stack overflow vulnerability was found in the Intel HD Audio device (intel-hda) of QEMU. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability. This flaw affects QEMU versions prior to 7.0.0.
CVE-2021-3750: A DMA reentrancy issue was found in the USB EHCI controller emulation of QEMU. EHCI does not verify if the Buffer Pointer overlaps with its MMIO region when it transfers the USB packets. Crafted content may be written to the controller's registers and trigger undesirable actions (such as reset) while the device is still transferring packets. This can ultimately lead to a use-after-free issue. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition, or potentially execute arbitrary code within the context of the QEMU process on the host. This flaw affects QEMU versions before 7.0.0.
CVE-2021-3929: A DMA reentrancy issue was found in the NVM Express Controller (NVME) emulation in QEMU. This CVE is similar to CVE-2021-3750 and, just like it, when the reentrancy write triggers the reset function nvme_ctrl_reset(), data structs will be freed leading to a use-after-free issue. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition or, potentially, executing arbitrary code within the context of the QEMU process on the host.
CVE-2022-4144: An out-of-bounds read flaw was found in the QXL display device emulation in QEMU. The qxl_phys2virt() function does not check the size of the structure pointed to by the guest physical address, potentially reading past the end of the bar space into adjacent pages. A malicious guest user could use this flaw to crash the QEMU process on the host causing a denial of service condition.
CVE-2023-2861: A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. The 9pfs server did not prohibit opening special files on the host side, potentially allowing a malicious client to escape from the exported 9p tree by creating and opening a device file in the shared folder.
CVE-2024-3446: 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-4467: 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-2020-15469: In QEMU 4.2.0, a MemoryRegionOps object may lack read/write callback methods, leading to a NULL pointer dereference.
CVE-2020-35504: A NULL pointer dereference flaw was found in the SCSI emulation support of QEMU in versions before 6.0.0. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
CVE-2020-35505: A NULL pointer dereference flaw was found in the am53c974 SCSI host bus adapter emulation of QEMU in versions before 6.0.0. This issue occurs while handling the 'Information Transfer' command. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
CVE-2020-35506: A use-after-free vulnerability was found in the am53c974 SCSI host bus adapter emulation of QEMU in versions before 6.0.0 during the handling of the 'Information Transfer' command (CMD_TI). This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service or potential code execution with the privileges of the QEMU process.

Created: 2026-04-23 Last update: 2026-07-27 10:31

32 security issues in bookworm high

There are 32 open security issues in bookworm.

14 important issues:

CVE-2026-6425:
CVE-2026-8343:
CVE-2026-8348:
CVE-2026-9238:
CVE-2026-12080: A flaw was found in the QEMU Guest Agent (qga). A local unprivileged user can exploit a vulnerability in the guest-ssh-add-authorized-keys command handler by manipulating symbolic links. This can occur either through a deterministic directory-symlink bypass or a Time-of-Check to Time-of-Use (TOCTOU) file-symlink race. Successful exploitation allows the attacker to gain ownership of arbitrary root-owned files or directories, leading to root access. This vulnerability requires an external management layer (e.g., libvirt) to trigger the affected code path.
CVE-2026-15578:
CVE-2026-15705:
CVE-2026-16043:
CVE-2026-48002:
CVE-2026-48003:
CVE-2026-48004:
CVE-2026-48914: A flaw was found in QEMU's virtio-blk device. The issue arises because the device does not properly validate the size of input descriptors before writing data. A malicious guest with high privileges could exploit this vulnerability by submitting a malformed virtio-blk SCSI request, leading to an out-of-bounds write in the host heap memory and a potential denial of service (DoS) for the QEMU process.
CVE-2026-61475:
CVE-2026-63319:

18 issues left for the package maintainer to handle:

CVE-2021-3735: (postponed; to be fixed through a stable update) A deadlock issue was found in the AHCI controller device of QEMU. It occurs on a software reset (ahci_reset_port) while handling a host-to-device Register FIS (Frame Information Structure) packet from the guest. A privileged user inside the guest could use this flaw to hang the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability.
CVE-2022-3872: (postponed; to be fixed through a stable update) An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.
CVE-2023-1386: (postponed; to be fixed through a stable update) A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. When a local user in the guest writes an executable file with SUID or SGID, none of these privileged bits are correctly dropped. As a result, in rare circumstances, this flaw could be used by malicious users in the guest to elevate their privileges within the guest and help a host local user to elevate privileges on the host.
CVE-2024-6519: (needs triaging) A use-after-free vulnerability was found in the QEMU LSI53C895A SCSI Host Bus Adapter emulation. This issue can lead to a crash or VM escape.
CVE-2024-7730: (needs triaging) A heap buffer overflow was found in the virtio-snd device in QEMU. When reading input audio in the virtio-snd input callback, virtio_snd_pcm_in_cb, the function did not check whether the iov can fit the data buffer. This issue can trigger an out-of-bounds write if the size of the virtio queue element is equal to virtio_snd_pcm_status, which makes the available space for audio data zero.
CVE-2024-8354: (needs triaging) 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-8612: (needs triaging) 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-2026-2243: (needs triaging) A flaw was found in QEMU. A specially crafted VMDK image could trigger an out-of-bounds read vulnerability, potentially leading to a 12-byte leak of sensitive information or a denial of service condition (DoS).
CVE-2026-3842: (needs triaging) A flaw was found in QEMU. This vulnerability allows a local attacker within a guest virtual machine to write data beyond its allocated memory. This occurs when cpu_physical_memory_map() returns a shorter length than expected, leading to an out-of-bounds write. Successful exploitation could result in unauthorized access to guest memory or corruption of heap-allocated objects, potentially causing information disclosure, data integrity issues, or a denial of service.
CVE-2026-3890: (needs triaging)
CVE-2026-5763: (needs triaging)
CVE-2019-12067: (postponed; to be fixed through a stable update) The ahci_commit_buf function in ide/ahci.c in QEMU allows attackers to cause a denial of service (NULL dereference) when the command header 'ad->cur_cmd' is null.
CVE-2020-25741: (postponed; to be fixed through a stable update) fdctrl_write_data in hw/block/fdc.c in QEMU 5.0.0 has a NULL pointer dereference via a NULL block pointer for the current drive.
CVE-2020-25742: (postponed; to be fixed through a stable update) pci_change_irq_level in hw/pci/pci.c in QEMU before 5.1.1 has a NULL pointer dereference because pci_get_bus() might not return a valid pointer.
CVE-2020-25743: (postponed; to be fixed through a stable update) hw/ide/pci.c in QEMU before 5.1.1 can trigger a NULL pointer dereference because it lacks a pointer check before an ide_cancel_dma_sync call.
CVE-2020-35503: (postponed; to be fixed through a stable update) A NULL pointer dereference flaw was found in the megasas-gen2 SCSI host bus adapter emulation of QEMU in versions before and including 6.0. This issue occurs in the megasas_command_cancelled() callback function while dropping a SCSI request. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
CVE-2021-20255: (postponed; to be fixed through a stable update) A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator of QEMU. This issue occurs while processing controller commands due to a DMA reentry issue. This flaw allows a guest user or process to consume CPU cycles or crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability.
CVE-2025-14876: (needs triaging) A flaw was found in the virtio-crypto device of QEMU. A malicious guest operating system can exploit a missing length limit in the AKCIPHER path, leading to uncontrolled memory allocation. This can result in a denial of service (DoS) on the host system by causing the QEMU process to terminate unexpectedly.

You can find information about how to handle these issues in the security team's documentation.

Created: 2023-06-10 Last update: 2026-07-27 10:31

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

https://salsa.debian.org/api/v4/projects/qemu-team%2Fqemu API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.

Created: 2026-07-16 Last update: 2026-07-27 08:36

2 bugs tagged patch in the BTS normal

The BTS contains patches fixing 2 bugs, consider including or untagging them.

Created: 2026-06-02 Last update: 2026-07-27 16:00

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2026-06-01 Last update: 2026-07-27 11:34

lintian reports 23 warnings normal

Lintian reports 23 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2026-07-27 Last update: 2026-07-27 04:19

debian/patches: 7 patches to forward upstream low

Among the 25 debian patches available in version 1:11.0.3+ds-2 of the package, we noticed the following issues:

7 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-07-27 14:32

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-07-27 13:30

testing migrations

excuses:
- Migrates after: gcc-15
- Migration status for qemu (1:11.0.2+ds-2 to 1:11.0.3+ds-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- ∙ ∙ Missing build on riscv64
- ∙ ∙ Piuparts check waiting for test results - https://piuparts.debian.org/sid/source/q/qemu.html
- ∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
- ∙ ∙ Autopkgtest for architecture-properties: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for cinder: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for cloud-utils: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for cryptsetup: amd64: Test triggered (will not be considered a regression) ♻ (reference ♻), arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for debos: amd64: Test triggered, arm64: Test triggered
- ∙ ∙ Autopkgtest for debusine: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered (will not be considered a regression) ♻ (reference ♻), i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for debvm: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for dracut: amd64: Test triggered, arm64: Test triggered, loong64: Test triggered (will not be considered a regression) ♻ (reference ♻), ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for dropbear: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for fai: amd64: Test triggered (will not be considered a regression) ♻ (reference ♻), arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for freedom-maker: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered (will not be considered a regression) ♻ (reference ♻), i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for gcc-arm-none-eabi: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered (will not be considered a regression) ♻ (reference ♻), i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for genimage: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for glance: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for golang-github-go-debos-fakemachine: amd64: Test triggered, arm64: Test triggered
- ∙ ∙ Autopkgtest for hare: amd64: Test triggered, arm64: Test triggered
- ∙ ∙ Autopkgtest for image-garden: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for incus: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for ironic: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for isa-support: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, ppc64el: Test triggered
- ∙ ∙ Autopkgtest for lava: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for libguestfs: amd64: Test triggered, arm64: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for libvhdi: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for libvirt: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for multipath-tools: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for nova: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Test triggered
- ∙ ∙ Autopkgtest for open-iscsi: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for os-autoinst: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for pkg-rocm-tools: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for python-oslo.utils: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for qbe: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for qemu: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered (will not be considered a regression) ♻ (reference ♻), i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for sbuild: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered (will not be considered a regression) ♻ (reference ♻), i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for shim: amd64: Test triggered, arm64: Test triggered
- ∙ ∙ Autopkgtest for syslinux: amd64: Test triggered, arm64: Test triggered (will not be considered a regression) ♻ (reference ♻), armhf: Test triggered (will not be considered a regression) ♻ (reference ♻), i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Test triggered
- ∙ ∙ Autopkgtest for systemd: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for vmdb2: amd64: Test triggered, arm64: Test triggered, armhf: Test triggered, i386: Test triggered, loong64: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ Lintian check waiting for test results on s390x, riscv64, loong64, ppc64el, i386, all, arm64, amd64 - info
- ∙ ∙ Reproducibility check waiting for results on amd64 - info
- ∙ ∙ Reproducibility check waiting for results on arm64 - info
- ∙ ∙ Reproducibility check waiting for results on armhf - info
- ∙ ∙ Reproducibility check waiting for results on i386 - info
- ∙ ∙ Too young, only 0 of 5 days old
- ∙ ∙ Built-Using: qemu gcc-15
- Not considered

news

[rss feed]

[2026-07-27] Accepted qemu 1:11.0.3+ds-2 (source) into unstable (Michael Tokarev)
[2026-07-26] Accepted qemu 1:11.0.3+ds-1 (source) into unstable (Michael Tokarev)
[2026-07-24] Accepted qemu 1:11.1.0~rc1+ds-1 (source) into experimental (Michael Tokarev)
[2026-07-21] Accepted qemu 1:11.0.2+ds-2~bpo13+1 (all amd64 source) into stable-backports (Debian FTP Masters) (signed by: Michael Tokarev)
[2026-07-21] Accepted qemu 1:11.1.0~rc0+ds-2 (source) into experimental (Michael Tokarev)
[2026-07-16] Accepted qemu 1:11.1.0~rc0+ds-1 (source) into experimental (Michael Tokarev)
[2026-07-14] qemu 1:11.0.2+ds-2 MIGRATED to testing (Debian testing watch)
[2026-07-04] Accepted qemu 1:10.0.11+ds-0+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
[2026-07-04] Accepted qemu 1:10.0.10+ds-0+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
[2026-07-01] Accepted qemu 1:11.0.2+ds-2 (source) into unstable (Michael Tokarev)
[2026-06-28] Accepted qemu 1:11.0.2+ds-1 (source) into unstable (Michael Tokarev)
[2026-06-25] qemu 1:11.0.1+ds-1 MIGRATED to testing (Debian testing watch)
[2026-06-01] Accepted qemu 1:11.0.1+ds-1 (source) into unstable (Michael Tokarev)
[2026-06-01] qemu 1:11.0.0+ds-2 MIGRATED to testing (Debian testing watch)
[2026-05-05] Accepted qemu 1:11.0.0+ds-2 (source) into unstable (Michael Tokarev)
[2026-04-22] Accepted qemu 1:11.0.0+ds-1 (source) into unstable (Michael Tokarev)
[2026-04-11] Accepted qemu 1:11.0.0~rc3+ds-1 (source) into experimental (Michael Tokarev)
[2026-04-06] qemu 1:10.2.2+ds-1 MIGRATED to testing (Debian testing watch)
[2026-04-03] Accepted qemu 1:11.0.0~rc2+ds-2 (source) into experimental (Michael Tokarev)
[2026-04-03] Accepted qemu 1:11.0.0~rc2+ds-1 (source) into experimental (Michael Tokarev)
[2026-03-26] Accepted qemu 1:11.0.0~rc1+ds-3 (source) into experimental (Michael Tokarev)
[2026-03-25] Accepted qemu 1:11.0.0~rc1+ds-2 (source) into experimental (Michael Tokarev)
[2026-03-24] Accepted qemu 1:11.0.0~rc1+ds-1 (source) into experimental (Michael Tokarev)
[2026-03-19] Accepted qemu 1:10.2.2+ds-1 (source) into unstable (Michael Tokarev)
[2026-03-19] Accepted qemu 1:11.0.0~rc0+ds-2 (source) into experimental (Michael Tokarev)
[2026-03-19] Accepted qemu 1:11.0.0~rc0+ds-1 (source) into experimental (Michael Tokarev)
[2026-03-07] Accepted qemu 1:10.0.8+ds-0+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
[2026-02-24] qemu 1:10.2.1+ds-1 MIGRATED to testing (Debian testing watch)
[2026-02-13] Accepted qemu 1:10.2.1+ds-1 (source) into unstable (Michael Tokarev)
[2026-01-18] qemu 1:10.2.0+ds-2 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 112 121
RC: 0
I&N: 50
M&W: 62 71
F&P: 0
patch: 2

links

homepage
lintian (0, 23)
buildd: logs, exp, reproducibility
popcon
browse source code
other distros
security tracker
l10n (-, 94)
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1:10.2.1+ds-1ubuntu3