Security update for xen
This update for xen fixes the following issues: - CVE-2021-3308: VUL-0: xen: IRQ vector leak on x86 (bsc#1181254, XSA-360) - CVE-2021-28687: VUL-0: xen: HVM soft-reset crashes toolstack (bsc#1183072, XSA-368) - CVE-2021-20257: VUL-0: xen: infinite loop issue in the e1000 NIC emulator (bsc#1182846) - CVE-2020-28368: VUL-0: xen: Intel RAPL sidechannel attack aka PLATYPUS attack aka (bsc#1178591, XSA-351) - L3: conring size for XEN HV's with huge memory to small. Inital Xen logs cut (bsc#1177204) - Kdump of HVM fails, soft-reset not handled by libxl (bsc#1179148) - OpenQA job causes libvirtd to dump core when running kdump inside domain (bsc#1181989) - Allow restart of xenwatchdogd, enable tuning of keep-alive interval and timeout options via XENWATCHDOGD_ARGS= (bsc#1178736) - The receiving side did detect holes in a to-be-allocated superpage, but allocated a superpage anyway. This resulted to over-allocation (bsc#1177112) - The receiving side may punch holes incorrectly into optimistically allocated superpages. Also reduce overhead in bitmap handling (bsc#1177112) - Upstream bug fixes (bsc#1027519)
02 / AFFECTED SOFTWARE
Affected packages
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
This update for xen fixes the following issues: - CVE-2021-3308: VUL-0: xen: IRQ vector leak on x86 (bsc#1181254, XSA-360) - CVE-2021-28687: VUL-0: xen: HVM soft-reset crashes toolstack (bsc#1183072, XSA-368) - CVE-2021-20257: VUL-0: xen: infinite loop issue in the e1000 NIC emulator (bsc#1182846) - CVE-2020-28368: VUL-0: xen: Intel RAPL sidechannel attack aka PLATYPUS attack aka (bsc#1178591, XSA-351) - L3: conring size for XEN HV's with huge memory to small. Inital Xen logs cut (bsc#1177204) - Kdump of HVM fails, soft-reset not handled by libxl (bsc#1179148) - OpenQA job causes libvirtd to dump core when running kdump inside domain (bsc#1181989) - Allow restart of xenwatchdogd, enable tuning of keep-alive interval and timeout options via XENWATCHDOGD_ARGS= (bsc#1178736) - The receiving side did detect holes in a to-be-allocated superpage, but allocated a superpage anyway. This resulted to over-allocation (bsc#1177112) - The receiving side may punch holes incorrectly into optimistically allocated superpages. Also reduce overhead in bitmap handling (bsc#1177112) - Upstream bug fixes (bsc#1027519)
05 / REFERENCES
Further evidence
- https://bugzilla.suse.com/1027519
- https://bugzilla.suse.com/1177112
- https://bugzilla.suse.com/1177204
- https://bugzilla.suse.com/1178591
- https://bugzilla.suse.com/1178736
- https://bugzilla.suse.com/1179148
- https://bugzilla.suse.com/1181254
- https://bugzilla.suse.com/1181989
- https://bugzilla.suse.com/1182846
- https://bugzilla.suse.com/1183072
- https://www.suse.com/security/cve/CVE-2020-28368
- https://www.suse.com/security/cve/CVE-2021-20257
- https://www.suse.com/security/cve/CVE-2021-28687
- https://www.suse.com/security/cve/CVE-2021-3308
- https://www.suse.com/support/update/announcement/2021/suse-su-20211023-1/