Debian Package Tracker
Register | Log in
Subscribe

qemu

Choose email to subscribe with

general
  • source: qemu (main)
  • version: 1:10.2.0+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+deb12u16
  • old-sec: 1:7.2+dfsg-7+deb12u15
  • old-bpo: 1:10.0.2+ds-2+deb13u1~bpo12+1
  • stable: 1:10.0.6+ds-0+deb13u2
  • stable-sec: 1:10.0.2+ds-2+deb13u1
  • testing: 1:10.1.2+ds-3
  • unstable: 1:10.2.0+ds-2
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+deb12u16: [.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.6+ds-0+deb13u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:10.0.7+ds-0+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:10.1.2+ds-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:10.2.0+ds-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:10.2.0+ds-2: [.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 (18 bugs: 0, 13, 5, 0)
  • qemu-system-xen
  • qemu-user (3 bugs: 0, 2, 1, 0)
  • qemu-user-binfmt (1 bugs: 0, 1, 0, 0)
  • qemu-utils (2 bugs: 0, 1, 1, 0)
action needed
1 binary package has unsatisfiable dependencies high
  • The dependencies of qemu-user-static=1:10.0.7+ds-0+deb13u1+b1 cannot be satisfied in unstable on i386, arm64, armhf, ppc64el, s390x, and amd64 because: conflict between qemu-user-binfmt and qemu-user-static
Created: 2025-12-19 Last update: 2026-01-14 22:33
13 security issues in trixie high

There are 13 open security issues in trixie.

1 important issue:
  • CVE-2026-0665:
12 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-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.
  • CVE-2025-14876: (needs triaging)

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

Created: 2023-06-11 Last update: 2026-01-14 21:30
11 security issues in sid high

There are 11 open security issues in sid.

11 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-6519: 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-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-2025-14876:
Created: 2022-07-04 Last update: 2026-01-14 21:30
14 security issues in forky high

There are 14 open security issues in forky.

14 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-6519: 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-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-0665:
  • 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-2025-11234: 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.
  • CVE-2025-12464: A stack-based buffer overflow was found in the QEMU e1000 network device. The code for padding short frames was dropped from individual network devices and moved to the net core code. The issue stems from the device's receive code still being able to process a short frame in loopback mode. This could lead to a buffer overrun in the e1000_receive_iov() function via the loopback code path. A malicious guest user could use this vulnerability to crash the QEMU process on the host, resulting in a denial of service.
  • CVE-2025-14876:
Created: 2025-08-09 Last update: 2026-01-14 21:30
2 bugs tagged patch in the BTS normal
The BTS contains patches fixing 2 bugs, consider including or untagging them.
Created: 2025-01-06 Last update: 2026-01-14 22:30
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: 2025-12-14 Last update: 2026-01-14 21:31
1 open merge request in Salsa normal
There is 1 open merge request for this package on Salsa. You should consider reviewing and/or merging these merge requests.
Created: 2025-11-25 Last update: 2026-01-14 16:48
14 low-priority security issues in bookworm low

There are 14 open security issues in bookworm.

14 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-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)

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

Created: 2023-06-10 Last update: 2026-01-14 21:30
debian/patches: 5 patches to forward upstream low

Among the 21 debian patches available in version 1:10.2.0+ds-1 of the package, we noticed the following issues:

  • 5 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: 2025-12-25 11:01
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.3 instead of 4.7.2).
Created: 2025-12-23 Last update: 2026-01-14 22:00
testing migrations
  • excuses:
    • Migration status for qemu (1:10.1.2+ds-3 to 1:10.2.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ Piuparts regression - https://piuparts.debian.org/sid/source/q/qemu.html
    • ∙ ∙ Autopkgtest for architecture-properties/0.2.6: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for cinder/2:27.0.0-4: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: No tests, superficial or marked flaky ♻, s390x: Test triggered
    • ∙ ∙ Autopkgtest for cloud-utils/0.33-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for cryptsetup/2:2.8.3-1: amd64: Test triggered (will not be considered a regression) ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for debusine: amd64: Test triggered, arm64: Test triggered (will not be considered a regression) ♻ (reference ♻), i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for debvm/0.5.0: amd64: Pass, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for dracut: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
    • ∙ ∙ Autopkgtest for dropbear/2025.89-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for edk2: i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for fai/6.5.2: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for freedom-maker/0.34: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for genimage/19-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for glance/2:31.0.0-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for image-garden/0.3-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for incus/6.0.5-7: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for ipmitool/1.8.19-10: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for ironic/1:32.0.0-6: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for ironic-python-agent/11.2.0-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for isa-support/27: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered
    • ∙ ∙ Autopkgtest for libguestfs/1:1.54.1-3.1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for libstdc++-riscv64-unknown-elf/7: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for libvhdi/20240509-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for libvirt/11.10.0-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for multipath-tools/0.13.0-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for nova/2:32.1.0-6: amd64: Pass, arm64: Regression ♻ (reference ♻), i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for open-iscsi/2.1.11-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for osk-sdl/0.67.1-4: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for python-oslo.utils/9.1.0-4: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for qbe/1.2-3: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for qemu/1:10.2.0+ds-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for sbuild/0.91.5: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for snek/1.13-1: amd64: Reference test triggered, but real test failed already ♻, arm64: Reference test triggered, but real test failed already ♻, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for syslinux/3:6.04~git20190206.bf6db5b4+dfsg1-3.2: amd64: Pass, arm64: Failed (not a regression) ♻ (reference ♻), i386: Test triggered, ppc64el: Test triggered (will not be considered a regression) ♻ (reference ♻), s390x: Test triggered (will not be considered a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for systemd/259-1: amd64: Pass, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Autopkgtest for vmdb2/0.41-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
    • ∙ ∙ Missing build on riscv64
    • ∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
    • ∙ ∙ Lintian check waiting for test results - info
    • ∙ ∙ Too young, only 0 of 5 days old
    • Additional info (not blocking):
    • ∙ ∙ Waiting for reproducibility test results on amd64 - info ♻
    • ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻
    • Not considered
news
[rss feed]
  • [2026-01-14] Accepted qemu 1:10.2.0+ds-2 (source) into unstable (Michael Tokarev)
  • [2026-01-01] Accepted qemu 1:7.2+dfsg-7+deb12u18 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • [2026-01-01] Accepted qemu 1:10.0.7+ds-0+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • [2025-12-24] Accepted qemu 1:10.2.0+ds-1 (source) into unstable (Michael Tokarev)
  • [2025-12-15] Accepted qemu 1:10.1.3+ds-1 (source) into unstable (Michael Tokarev)
  • [2025-12-14] qemu 1:10.1.2+ds-3 MIGRATED to testing (Debian testing watch)
  • [2025-12-07] Accepted qemu 1:7.2+dfsg-7+deb12u17 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • [2025-11-19] Accepted qemu 1:10.2.0~rc1+ds-1 (source) into experimental (Michael Tokarev)
  • [2025-11-13] Accepted qemu 1:10.1.2+ds-3 (source) into unstable (Michael Tokarev)
  • [2025-11-05] Accepted qemu 1:10.0.6+ds-0+deb13u2 (source) into proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • [2025-11-04] Accepted qemu 1:10.1.2+ds-2 (source) into unstable (Michael Tokarev)
  • [2025-10-31] Accepted qemu 1:10.0.6+ds-0+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • [2025-10-25] qemu 1:10.1.2+ds-1 MIGRATED to testing (Debian testing watch)
  • [2025-10-21] Accepted qemu 1:10.1.2+ds-1 (source) into unstable (Michael Tokarev)
  • [2025-10-13] qemu 1:10.1.1+ds-1 MIGRATED to testing (Debian testing watch)
  • [2025-10-09] Accepted qemu 1:10.1.1+ds-1 (source) into unstable (Michael Tokarev)
  • [2025-09-18] qemu 1:10.1.0+ds-5 MIGRATED to testing (Debian testing watch)
  • [2025-09-13] Accepted qemu 1:10.1.0+ds-5 (source) into unstable (Michael Tokarev)
  • [2025-09-11] Accepted qemu 1:10.1.0+ds-4 (source) into unstable (Michael Tokarev)
  • [2025-09-10] Accepted qemu 1:10.1.0+ds-3 (source) into unstable (Michael Tokarev)
  • [2025-09-09] Accepted qemu 1:5.2+dfsg-11+deb11u5 (source) into oldoldstable-security (Santiago Ruano Rincón)
  • [2025-09-05] Accepted qemu 1:10.0.2+ds-2+deb13u1~bpo12+1 (source) into oldstable-backports (Michael Tokarev)
  • [2025-09-02] qemu 1:10.1.0+ds-2 MIGRATED to testing (Debian testing watch)
  • [2025-08-29] Accepted qemu 1:10.1.0+ds-2 (source) into unstable (Michael Tokarev)
  • [2025-08-27] Accepted qemu 1:10.1.0+ds-1 (source) into unstable (Michael Tokarev)
  • [2025-08-25] Accepted qemu 1:7.2+dfsg-7+deb12u16 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • [2025-08-25] Accepted qemu 1:10.0.3+ds-0+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • [2025-08-25] qemu 1:10.0.3+ds-4 MIGRATED to testing (Debian testing watch)
  • [2025-08-25] Accepted qemu 1:7.2+dfsg-7+deb12u15 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • [2025-08-25] Accepted qemu 1:10.0.2+ds-2+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Michael Tokarev)
  • 1
  • 2
bugs [bug history graph]
  • all: 114 123
  • RC: 0
  • I&N: 50
  • M&W: 64 73
  • F&P: 0
  • patch: 2
links
  • homepage
  • buildd: logs, reproducibility, debcheck
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • l10n (-, 94)
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 1:10.1.0+ds-5ubuntu4
  • 94 bugs (2 patches)

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing