enterprise-support team mailing list archive

[Launchpad Bug Tracker <1914145@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package qemu - 1:5.2+dfsg-6ubuntu2

---------------
qemu (1:5.2+dfsg-6ubuntu2) hirsute; urgency=medium

  * d/p/u/lp-1916705-disas-Fix-build-with-glib2.0-2.67.3.patch: Fix FTFBS due
    to glib2.0 >=2.67.3 (LP: #1916705)

qemu (1:5.2+dfsg-6ubuntu1) hirsute; urgency=medium

  * Merge with Debian unstable, includes fixes for
    - build operates differently if source is a git repo (LP: #1887535)
    Remaining changes:
    - qemu-kvm to systemd unit
      - d/qemu-kvm-init: script for QEMU KVM preparation modules, ksm,
        hugepages and architecture specifics
      - d/qemu-system-common.qemu-kvm.service: systemd unit to call
        qemu-kvm-init
      - d/qemu-system-common.install: install helper script
      - d/qemu-system-common.qemu-kvm.default: defaults for
        /etc/default/qemu-kvm
      - d/rules: call dh_installinit and dh_installsystemd for qemu-kvm
    - Distribution specific machine type (LP: 1304107 1621042)
      - d/p/ubuntu/define-ubuntu-machine-types.patch: distro machine types
      - d/qemu-system-x86.NEWS Info on fixed machine type definitions
        for host-phys-bits=true (LP: 1776189)
      - add an info about -hpb machine type in debian/qemu-system-x86.NEWS
      - provide pseries-bionic-2.11-sxxm type as convenience with all
        meltdown/spectre workarounds enabled by default. (LP: 1761372).
      - ubuntu-q35 alias added to auto-select the most recent q35 ubuntu type
    - Enable nesting by default
      - d/p/ubuntu/enable-svm-by-default.patch: Enable nested svm by default
        in qemu64 on amd
        [ No more strictly needed, but required for backward compatibility ]
    - improved dependencies
      - Make qemu-system-common depend on qemu-block-extra
      - Make qemu-utils depend on qemu-block-extra
      - let qemu-utils recommend sharutils
    - tolerate ipxe size change on migrations to >=18.04 (LP: 1713490)
      - d/p/ubuntu/pre-bionic-256k-ipxe-efi-roms.patch: old machine types
        reference 256k path
      - d/control-in: depend on ipxe-qemu-256k-compat-efi-roms to be able to
        handle incoming migrations from former releases.
    - d/control-in: Disable capstone disassembler library support (universe)
    - d/qemu-system-x86.README.Debian: add info about updated nesting changes
    - d/control*, d/rules: disable xen by default, but provide universe
      package qemu-system-x86-xen as alternative
      [includes compat links changes of 5.0-5ubuntu4]
    - allow qemu to load old modules post upgrade (LP 1847361)
      - Drop d/qemu-block-extra.*.in, d/qemu-system-gui.*.in
      - d/rules: Drop generating package version into maintainer scripts
      - d/qemu-system-gui.prerm: add no-op prerm to overcome upgrade issues on
        the bad old prerm (LP 1906245 1905377)
    - d/p/ubuntu/lp-1907789-build-no-pie-is-no-functional-liker-flag.patch: fix
      ld usage of -no-pie (LP 1907789)
  * Added changes
    - d/p/u/lp-1916230-hw-s390x-fix-build-for-virtio-9p-ccw.patch: fix
      virtio-9p-ccw being missing (LP: #1916230)

qemu (1:5.2+dfsg-6) unstable; urgency=medium

  * deprecate qemu-debootstrap. It is not needed anymore with
    binfmt F flag, since everything now works without --foreign
    debootstrap argument and copying the right qemu binary into
    the chroot. Closes: #901197
  * fix the brown-paper bag bug: wrong argument order
    in the linux-user-binfmt patch (really closes: #970460)

qemu (1:5.2+dfsg-5) unstable; urgency=medium

  * d/rules: ensure b/ subdir exists before building palcode and qboot
  * d/changelog: #959530 is not fixed by 5.2+dfsg-4
  * 3 virtiofsd patches Closes: #980814, CVE-2020-35517
    virtiofsd: potential privileged host device access from guest
    - virtiofsd-extract-lo_do_open-from-lo_open.patch
    - virtiofsd-optionally-return-inode-pointer-from-lo_do_lookup.patch
    - virtiofsd-prevent-opening-of-special-files-CVE-2020-35517.patch

qemu (1:5.2+dfsg-4) unstable; urgency=medium

  [ Michael Tokarev ]
  * require libfdt >= 1.5.0-2 due to #931046
  * qemu-user: attempt to preserve argv[0] when run under binfmt
    (Closes: #970460)
    This changes the enterpreter name for all linux-user registered
    binfmts, so it potentially can break stuff.  The actual binary
    being registered now is /usr/libexec/qemu-binfmt/foo-binfmt-P,
    which is a symlink to actual /usr/lib/qemu-foo[-static].
  * ignore .git-submodule-status when building source
  * some security fixes from upstream:
    o arm_gic-fix-interrupt-ID-in-GICD_SGIR-CVE-2021-20221.patch
      Closes: CVE-2021-20221
      GIC (armv7): out-of-bound heap buffer access via an interrupt ID field
    o 9pfs-Fully-restart-unreclaim-loop-CVE-2021-20181.patch
      Closes: CVE-2021-20181
  * non-security fixes from upstream:
    pc-bios-descriptors-fix-paths-in-json-files.patch - fixes wrong paths
    in edk2-firmware-related json files introduced in 5.2

  [ Christian Ehrhardt ]
  * d/control-in: avoid version mismatch of installed binaries
    (Closes: #956377)

  [ Dan Streetman ]
  * Backport configure param --with-git-submodules and set to 'ignore'

 -- Christian Ehrhardt <christian.ehrhardt@xxxxxxxxxxxxx>  Wed, 24 Feb
2021 08:39:09 +0100

** Changed in: qemu (Ubuntu)
       Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-35517

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-20181

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-20221

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to samba in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1914145

Title:
  Please merge liburing 0.7-3 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liburing/+bug/1914145/+subscriptions