Changes since 4.5.3: mostly bugfixes, including fixes for
security issues XSA-172, XSA-173, XSA-175, XSA-176, XSA-178, XSA-179, XSA-180,
XSA-181, XSA-182, XSA-183, XSA-184, XSA-185, XSA-186 and XSA-187.
All but XSA-175 were already fixed in pkgsrc.
Complete list of changes and links to the XSA advisories:
https://www.xenproject.org/downloads/xen-archives/xen-45-series/xen-455.html
breaks the build. It does exist in NetBSD 7's gcc 4.8.4, but the
build is successful without it. So only apply the flag for gcc 5,
as it is necessary for 5.4.0.
Report from jnemeth@
While there also add patches for security issues XSA-172, XSA-173 and XSA-179
(others between 170 and 179 are either not yet public, or linux-only).
Upstream changes since 4.5.2:
- security issues up to XSA-170 are fixed (these were already patched
in pkgsrc).
- other minor performances and functionality fixes.
full changelog at:
http://www.xenproject.org/downloads/xen-archives/xen-45-series/xen-453.html
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Note that the patch for XSA135 for qemu-traditional, which was
no applied to the 4.5 branch before the release due to an oversight,
is applied here (xentools45/patches/patch-XSA135).
Selected entries from the relase notes:
a246727: cpupool: fix shutdown with cpupools with different schedulers [Dario Faggioli]
5b2f480: libelf: fix elf_parse_bsdsyms call [Roger Pau Monné]
8faef24: VT-d: extend quirks to newer desktop chipsets [Jan Beulich]
24fcf17: x86/VPMU: add lost Intel processor [Alan Robinson]
131889c: x86/crash: don't use set_fixmap() in the crash path [Andrew Cooper]
8791a30: x86/apic: Disable the LAPIC later in smp_send_stop() [Andrew Cooper]
fbd26f2: x86/pvh: disable posted interrupts [Roger Pau Monné]
0d8cbca: libxl: In libxl_set_vcpuonline check for maximum number of VCPUs against the cpumap. [Konrad Rzeszutek Wilk]
bf06e40: libxl: event handling: ao_inprogress does waits while reports outstanding [Ian Jackson]
97051bd: libxl: event handling: Break out ao_work_outstanding [Ian Jackson]
0bc9f98: x86/traps: loop in the correct direction in compat_iret() [Andrew Cooper]
fcfbdb4: gnttab: add missing version check to GNTTABOP_swap_grant_ref handling [Jan Beulich]
09f76cb: cpupools: avoid crashing if shutting down with free CPUs [Dario Faggioli]
f237ee4: cpupool: assigning a CPU to a pool can fail [Dario Faggioli]
b986072: xen: common: Use unbounded array for symbols_offset. [Ian Campbell]
5eac1be: x86/irq: limit the maximum number of domain PIRQs [Andrew Cooper]
9c3d34d: x86: don't unconditionally touch the hvm_domain union during domain construction [Andrew Cooper]
9d5b2b0: tools/xenconsoled: Increase file descriptor limit [Andrew Cooper]
cfc4c43: ocaml/xenctrl: Fix stub_xc_readconsolering() [Andrew Cooper]
032673c: ocaml/xenctrl: Make failwith_xc() thread safe [Andrew Cooper]
c91ed88: ocaml/xenctrl: Check return values from hypercalls [Andrew Cooper]
fa62913: libxl: Domain destroy: fork [Ian Jackson]
c9b13f3: libxl: Domain destroy: unlock userdata earlier [Ian Jackson]
0b19348: libxl: In domain death search, start search at first domid we want [Ian Jackson]
ddfe333: x86: don't change affinity with interrupt unmasked [Jan Beulich]
bf30232: x86: don't clear high 32 bits of RAX on sub-word guest I/O port reads [Jan Beulich]
a824bf9: x86_emulate: fix EFLAGS setting of CMPXCHG emulation [Eugene Korenevsky]
f653b7f: x86/hvm: implicitly disable an ioreq server when it is destroyed [Paul Durrant]
8dbdcc3: x86/hvm: actually release ioreq server pages [Paul Durrant]
56fe488: x86/hvm: fix the unknown nested vmexit reason 80000021 bug [Liang Li]
4a52101: VT-d: improve fault info logging [Jan Beulich]
5a7c042: x86/MSI: fix error handling [Jan Beulich]
51d8325: LZ4 : fix the data abort issue [JeHyeon Yeon]
0327c93: hvmloader: don't treat ROM BAR like other BARs [Jan Beulich]
f2e08aa: domctl/sysctl: don't leak hypervisor stack to toolstacks [Andrew Cooper]
3771b5a: arm64: fix fls() [Jan Beulich]
9246d2e: domctl: don't allow a toolstack domain to call domain_pause() on itself [Andrew Cooper]
f5bca81: Limit XEN_DOMCTL_memory_mapping hypercall to only process up to 64 GFNs (or less) [Konrad Rzeszutek Wilk]
7fe1c1b: x86: don't apply reboot quirks if reboot set by user [Ross Lagerwall]
969df12: Revert "cpupools: update domU's node-affinity on the cpupool_unassign_cpu() path" [Jan Beulich]
483c6cd: honor MEMF_no_refcount in alloc_heap_pages() [Jan Beulich]
6616c4d: tools: libxl: Explicitly disable graphics backends on qemu cmdline [Ian Campbell]
d0b141e: x86/tboot: invalidate FIX_TBOOT_MAP_ADDRESS mapping after use [Jan Beulich]
902998e: x86emul: fully ignore segment override for register-only operations [Jan Beulich]
25c6ee8: pre-fill structures for certain HYPERVISOR_xen_version sub-ops [Aaron Adams]
7ef0364: x86/HVM: return all ones on wrong-sized reads of system device I/O ports [Jan Beulich]
3665563: tools/libxc: Don't leave scratch_pfn uninitialised if the domain has no memory [Andrew Cooper]
75ac8cf: x86/nmi: fix shootdown of pcpus running in VMX non-root mode [Andrew Cooper]
1e44c92: x86/hvm: explicitly mark ioreq server pages dirty [Paul Durrant]
2bfef90: x86/hvm: wait for at least one ioreq server to be enabled [Paul Durrant]
d976397: x86/VPMU: disable when NMI watchdog is on [Boris Ostrovsky]
84f2484: libxc: introduce a per architecture scratch pfn for temporary grant mapping [Julien Grall]
6302c61: Install libxlutil.h [Jim Fehlig]
d8e78d6: bunzip2: off by one in get_next_block() [Dan Carpenter]
8a855b3: docs/commandline: correct information for 'x2apic_phys' parameter [Andrew Cooper]
3a777be: x86: vcpu_destroy_pagetables() must not return -EINTR [Konrad Rzeszutek Wilk]
1acb3b6: handle XENMEM_get_vnumainfo in compat_memory_op [Wei Liu]
4eec09f: x86: correctly check for sub-leaf zero of leaf 7 in pv_cpuid() [Jan Beulich]
7788cbb: x86: don't expose XSAVES capability to PV guests [Jan Beulich]
4cfc54b: xsm/evtchn: never pretend to have successfully created a Xen event channel [Andrew Cooper]
2fdd521: common/memory: fix an XSM error path [Jan Beulich]
ad83ad9: x86emul: tighten CLFLUSH emulation [Jan Beulich]
1928318: dt-uart: use ':' as separator between path and options [Ian Campbell]
9ae1853: libxl: Don't ignore error when we fail to give access to ioport/irq/iomem [Julien Grall]
In addition, this release also contains the following fixes to qemu-traditional:
afaa35b: ... by default. Add a per-device "permissive" mode similar to pciback's to allow restoring previous behavior (and hence break security again, i.e. should be used only for trusted guests). [Jan Beulich]
3cff7ad: Since the next patch will turn all not explicitly described fields read-only by default, those fields that have guest writable bits need to be given explicit descriptors. [Jan Beulich]
ec61b93: The adjustments are solely to make the subsequent patches work right (and hence make the patch set consistent), namely if permissive mode (introduced by the last patch) gets used (as both reserved registers and reserved fields must be similarly protected from guest access in default mode, but the guest should be allowed access to them in permissive mode). [Jan Beulich]
37c77b8: xen_pt_emu_reg_pcie[]'s PCI_EXP_DEVCAP needs to cover all bits as read- only to avoid unintended write-back (just a precaution, the field ought to be read-only in hardware). [Jan Beulich]
2dc4059: This is just to avoid having to adjust that calculation later in multiple places. [Jan Beulich]
29d9566: xen_pt_pmcsr_reg_write() needs an adjustment to deal with the RW1C nature of the not passed through bit 15 (PCI_PM_CTRL_PME_STATUS). [Jan Beulich]
2e19270: There's no point in xen_pt_pmcsr_reg_{read,write}() each ORing PCI_PM_CTRL_STATE_MASK and PCI_PM_CTRL_NO_SOFT_RESET into a local emu_mask variable - we can have the same effect by setting the field descriptor's emu_mask member suitably right away. Note that xen_pt_pmcsr_reg_write() is being retained in order to allow later patches to be less intrusive. [Jan Beulich]
751d20d: Without this the actual XSA-131 fix would cause the enable bit to not get set anymore (due to the write back getting suppressed there based on the OR of emu_mask, ro_mask, and res_mask). [Jan Beulich]
51f3b5b: ... to avoid allowing the guest to cause the control domain's disk to fill. [Jan Beulich]
7f99bb9: It's being used by the hypervisor. For now simply mimic a device not capable of masking, and fully emulate any accesses a guest may issue nevertheless as simple reads/writes without side effects. [Jan Beulich]
6fc82bf: The old logic didn't work as intended when an access spanned multiple fields (for example a 32-bit access to the location of the MSI Message Data field with the high 16 bits not being covered by any known field). Remove it and derive which fields not to write to from the accessed fields' emulation masks: When they're all ones, there's no point in doing any host write. [Jan Beulich]
e42b84c: fdc: force the fifo access to be in bounds of the allocated buffer [Petr Matousek]
62e4158: xen: limit guest control of PCI command register [Jan Beulich]
3499745: cirrus: fix an uninitialized variable [Jan Beulich]
This release also contains the security fixes for XSA-117 to XSA-136, with the exception of XSA-124 which documents security risks of non-standard PCI device functionality that cannot be addressed in software. It also includes an update to XSA-98 and XSA-59.
Privilege escalation via emulated floppy disk drive
The code in qemu which emulates a floppy disk controller did not
correctly bounds check accesses to an array and therefore was
vulnerable to a buffer overflow attack.
A guest which has access to an emulated floppy device can exploit this
vulnerability to take over the qemu process elevating its privilege to
that of the qemu process.
All Xen systems running x86 HVM guests without stubdomains are
vulnerable to this depending on the specific guest configuration. The
default configuration is vulnerable.
Guests using either the traditional "qemu-xen" or upstream qemu device
models are vulnerable.
Guests using a qemu-dm stubdomain to run the device model are only
vulnerable to takeover of that service domain.
Systems running only x86 PV guests are not vulnerable.
ARM systems are not vulnerable.
x86emul: fully ignore segment override for register-only operations
For ModRM encoded instructions with register operands we must not
overwrite ea.mem.seg (if a - bogus in that case - segment override was
present) as it aliases with ea.reg.
This is CVE-2015-2151 / XSA-123.
xenkernel45:
File "/tmp/pkgsrc/sysutils/xenkernel45/work.x86_64/xen-4.5.0/xen/tools/compat-
build-source.py", line 30
print line.rstrip()
^
SyntaxError: invalid syntax
xentools45:
File "mkchecker.py", line 40, in <module>
if compat_arches.has_key(a):
AttributeError: 'dict' object has no attribute 'has_key'
...
XXX Assume the same is true for python 3.4 and mark as not for 33 34
guests operating systems on a single machine. Guest OSes (also
called "domains") require a modified kernel which supports Xen
hypercalls in replacement to access to the physical hardware. At
boot, the xen kernel is loaded along with the guest kernel for the
first domain (called domain0). domain0 has privileges to access
the physical hardware (PCI and ISA devices), administrate other
domains and provide virtual devices (disks and network) to other
domains.
xenkernel45 and xentools45 contains the kernel and tools from
the Xen 4.5.x branch
