{"id":"CVE-2021-28692","aliases":["ALPINE-CVE-2021-28692","DEBIAN-CVE-2021-28692","DSA-4931-1","EUVD-2021-15349","GHSA-23j5-p74r-rvqm","SUSE-SU-2021:14848-1","SUSE-SU-2021:2922-1","SUSE-SU-2021:2923-1","SUSE-SU-2021:2924-1","SUSE-SU-2021:2925-1","SUSE-SU-2021:2943-1","SUSE-SU-2021:2955-1","SUSE-SU-2021:2957-1","SUSE-SU-2021:3322-1","UBUNTU-CVE-2021-28692","openSUSE-SU-2021:1236-1","openSUSE-SU-2021:2923-1"],"status":"published","title":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in...","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","severity":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.00287,"percentile":0.21359,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-269"],"published":"2021-06-15T00:00:00Z","modified":"2026-10-23T18:03:28Z","fixes":[{"ecosystem":"Alpine:v3.11","package":"xen","fixed_in":["4.13.3-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.12","package":"xen","fixed_in":["4.13.3-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.13","package":"xen","fixed_in":["4.14.1-r3"],"sources":["osv"]},{"ecosystem":"Alpine:v3.14","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.16","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"xen","fixed_in":["4.15.0-r1"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"xen","fixed_in":["4.14.2+25-gb6a8c4f72d-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"xen","fixed_in":["4.14.2+25-gb6a8c4f72d-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"xen","fixed_in":["4.14.2+25-gb6a8c4f72d-1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.11","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.13.3-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.12","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.13.3-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.13","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.14.1-r3"}]}]},{"source":"osv","ecosystem":"Alpine:v3.14","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.16","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"4.15.0-r1"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.2+25-gb6a8c4f72d-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.2+25-gb6a8c4f72d-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.2+25-gb6a8c4f72d-1"}]}]},{"source":"osv","ecosystem":"Debian:10","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.4+107-gef32c7afa2-1"}]}],"versions":["4.11.1+92-g6c33308a8d-2","4.11.3+24-g14b62ab3e5-1","4.11.3+24-g14b62ab3e5-1~deb10u1","4.11.4+24-gddaaccbbab-1","4.11.4+24-gddaaccbbab-1~deb10u1","4.11.4+37-g3263f257ca-1","4.11.4+57-g41a822c392-1","4.11.4+57-g41a822c392-2","4.11.4+99-g8bce4698f6-1","4.11.4-1"],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_50-61.67.1"}]}],"bundled":17},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP2","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.3_02-3.34.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP2","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.3_02-3.34.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Micro 5.0","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.3_02-3.34.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP3","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.2_04-3.9.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP3","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.2_04-3.9.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP5","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.49.1"}]}],"bundled":15},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.49.1"}]}],"bundled":15},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.49.1"}]}],"bundled":15},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP1-BCL","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP1-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP1","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.0","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Manager Retail Branch Server 4.0","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Manager Server 4.0","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 6","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.4_12-3.52.1"}]}],"bundled":11},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15-ESPOS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.4_26-3.61.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.4_26-3.61.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.4_26-3.61.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 9","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.4_20-2.60.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud Crowbar 9","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.4_20-2.60.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.4_20-2.60.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP4-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.4_20-2.60.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:HPE Helion OpenStack 8","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.4_20-3.91.1"}]}],"bundled":13},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 8","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.4_20-3.91.1"}]}],"bundled":13},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud Crowbar 8","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.4_20-3.91.1"}]}],"bundled":13},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.4_20-3.91.1"}]}],"bundled":13},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.4_20-3.91.1"}]}],"bundled":13},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3-BCL","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.9.4_20-3.91.1"}]}],"bundled":13},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-BCL","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.7.6_16-43.79.5"}]}],"bundled":13},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.5.1-0ubuntu1","4.5.1-0ubuntu2","4.6.0-1ubuntu1","4.6.0-1ubuntu2","4.6.0-1ubuntu4","4.6.0-1ubuntu4.1","4.6.0-1ubuntu4.2","4.6.0-1ubuntu4.3","4.6.5-0ubuntu1","4.6.5-0ubuntu1.1","4.6.5-0ubuntu1.2","4.6.5-0ubuntu1.4"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.9.0-0ubuntu3","4.9.0-0ubuntu4","4.9.2-0ubuntu1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.9.2-0ubuntu2","4.9.2-0ubuntu6","4.9.2-0ubuntu7","4.11.3+24-g14b62ab3e5-1ubuntu1","4.11.3+24-g14b62ab3e5-1ubuntu2","4.11.3+24-g14b62ab3e5-1ubuntu2.2","4.11.3+24-g14b62ab3e5-1ubuntu2.3"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.11.4+24-gddaaccbbab-1ubuntu2","4.16.0-1~ubuntu2","4.16.0-1~ubuntu2.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.17.2-1","4.17.2+55-g0b56bed864-1","4.17.2+76-ge1f9cb16e2-1","4.17.2+76-ge1f9cb16e2-1ubuntu1","4.17.3+10-g091466ba55-1","4.17.3+10-g091466ba55-1.1ubuntu2","4.17.3+10-g091466ba55-1.1ubuntu3"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.20.0-1ubuntu1","4.20.0+68-g35cb38b222-1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.20.2+7-g1badcf5035-2build2","4.20.2+37-g61ff35323e-1ubuntu1","4.20.3+127-gc42374a105-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.20.0+68-g35cb38b222-1","4.20.2+7-g1badcf5035-2","4.20.2+7-g1badcf5035-2build2"]},{"source":"osv","ecosystem":"openSUSE:Leap 15.2","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.3_02-lp152.2.27.1"}]}],"bundled":11},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.2_04-3.9.1"}]}],"bundled":11}],"products":[{"vendor":"xen","product":"xen"}],"references":[{"url":"https://xenbits.xenproject.org/xsa/advisory-373.txt","tags":["x_refsource_MISC","x_transferred","Vendor Advisory","advisory"]},{"url":"https://security.gentoo.org/glsa/202107-30","tags":["vendor-advisory","x_refsource_GENTOO","x_transferred","Mitigation","Third Party Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-28692"},{"url":"https://github.com/advisories/GHSA-23j5-p74r-rvqm"},{"url":"https://security.alpinelinux.org/vuln/CVE-2021-28692","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2021-28692","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-202114848-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1182654","tags":["report"]},{"url":"https://bugzilla.suse.com/1186013","tags":["report"]},{"url":"https://bugzilla.suse.com/1186429","tags":["report"]},{"url":"https://bugzilla.suse.com/1186433","tags":["report"]},{"url":"https://bugzilla.suse.com/1186434","tags":["report"]},{"url":"https://bugzilla.suse.com/1187369","tags":["report"]},{"url":"https://bugzilla.suse.com/1187376","tags":["report"]},{"url":"https://bugzilla.suse.com/1187378","tags":["report"]},{"url":"https://bugzilla.suse.com/1189150","tags":["report"]},{"url":"https://bugzilla.suse.com/1189376","tags":["report"]},{"url":"https://bugzilla.suse.com/1189378","tags":["report"]},{"url":"https://bugzilla.suse.com/1189632","tags":["report"]},{"url":"https://bugzilla.suse.com/1192526","tags":["report"]},{"url":"https://bugzilla.suse.com/1192554","tags":["report"]},{"url":"https://bugzilla.suse.com/1192555","tags":["report"]},{"url":"https://bugzilla.suse.com/1192559","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-0089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3592","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3930","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212922-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1027519","tags":["report"]},{"url":"https://bugzilla.suse.com/1137251","tags":["report"]},{"url":"https://bugzilla.suse.com/1176189","tags":["report"]},{"url":"https://bugzilla.suse.com/1179148","tags":["report"]},{"url":"https://bugzilla.suse.com/1179246","tags":["report"]},{"url":"https://bugzilla.suse.com/1180491","tags":["report"]},{"url":"https://bugzilla.suse.com/1181989","tags":["report"]},{"url":"https://bugzilla.suse.com/1183877","tags":["report"]},{"url":"https://bugzilla.suse.com/1185682","tags":["report"]},{"url":"https://bugzilla.suse.com/1186428","tags":["report"]},{"url":"https://bugzilla.suse.com/1188050","tags":["report"]},{"url":"https://bugzilla.suse.com/1189373","tags":["report"]},{"url":"https://bugzilla.suse.com/1189380","tags":["report"]},{"url":"https://bugzilla.suse.com/1189381","tags":["report"]},{"url":"https://bugzilla.suse.com/1189882","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28700","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212923-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1183243","tags":["report"]},{"url":"https://bugzilla.suse.com/1187406","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212924-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1180846","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212925-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212943-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212955-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1181254","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3308","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20212957-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20213322-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2021-28692","tags":["report"]},{"url":"https://xenbits.xen.org/xsa/advisory-373.html","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-28692","tags":["report"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/VYJVCSKTOQY75TLGWH3HDYZAS33JTOTQ/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/JLC632KAG76ZVELO6CCNNSZVUXPDVXOQ/","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2021-28692","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","status":"published","published":"2021-06-30T10:27:57Z","modified":"2024-08-03T21:47:33.19Z","updated_at":"2026-11-02T14:33:08.811269Z"}],"euvd":[{"id":"EUVD-2021-15349","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","status":"published","published":"2021-06-30T10:27:57Z","modified":"2024-08-03T21:47:33Z","updated_at":"2026-11-03T03:24:46.117926Z"}],"ghsa":[{"id":"GHSA-23j5-p74r-rvqm","title":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in...","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","status":"published","published":"2022-05-24T19:06:40Z","modified":"2023-01-30T05:00:34Z","cwes":["CWE-269"],"updated_at":"2026-11-02T14:46:14.069279Z"}],"nvd":[{"id":"CVE-2021-28692","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","status":"published","published":"2021-06-30T11:15:08.087Z","modified":"2026-06-17T03:46:48.42Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":5.6,"vector":"AV:L/AC:L/Au:N/C:P/I:N/A:C","level":"medium","assessor":"primary"}],"cwes":["CWE-269"],"updated_at":"2026-11-02T14:06:55.259633Z"}],"osv":[{"id":"ALPINE-CVE-2021-28692","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","status":"published","published":"2021-06-30T11:15:08.087Z","modified":"2026-10-23T17:17:56.17284593Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:27:48.646074Z"},{"id":"CVE-2021-28692","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","status":"published","published":"2021-06-30T11:15:08.087Z","modified":"2026-03-15T22:37:00.439133Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:19.129331Z"},{"id":"DEBIAN-CVE-2021-28692","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","status":"published","published":"2021-06-30T11:15:08.087Z","modified":"2026-10-23T18:03:28.22961255Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:34.94143Z"},{"id":"UBUNTU-CVE-2021-28692","description":"inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.","status":"published","published":"2021-06-30T11:15:00Z","modified":"2026-10-17T12:56:14.921789975Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:26.779273Z"},{"id":"DSA-4931-1","title":"xen - security update","status":"published","published":"2021-06-15T00:00:00Z","modified":"2026-03-09T02:10:59.403168Z","updated_at":"2026-11-02T15:46:17.19998Z"},{"id":"openSUSE-SU-2021:1236-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nUpdate to Xen 4.13.3 general bug fix release (bsc#1027519).\n\nSecurity issues fixed:\n\n- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).\n\nOther issues fixed:\n\n- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)\n- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)\n- Fixed shell macro expansion in the spec file, so that ExecStart=\n  in xendomains-wait-disks.service is created correctly (bsc#1183877)\n- Upstream bug fixes (bsc#1027519)\n- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).\n- xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU during shutdown (bsc#1176189).\n- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n\nThis update was imported from the SUSE:SLE-15-SP2:Update update project.","status":"published","published":"2021-09-07T09:31:43Z","modified":"2026-02-04T02:28:33.693969Z","updated_at":"2026-11-02T16:58:32.266854Z"},{"id":"openSUSE-SU-2021:2923-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nUpdate to Xen 4.13.3 general bug fix release (bsc#1027519).\n\nSecurity issues fixed:\n\n- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).\n\nOther issues fixed:\n\n- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)\n- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)\n- Fixed shell macro expansion in the spec file, so that ExecStart=\n  in xendomains-wait-disks.service is created correctly (bsc#1183877)\n- Upstream bug fixes (bsc#1027519)\n- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).\n- xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU during shutdown (bsc#1176189).\n- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).\n- Some long deprecated commands were finally removed in qemu6. Adjust libxl to use supported commands (bsc#1183243).\n- Update logrotate.conf, move global options into per-file sections to prevent globbering of global state (bsc#1187406).\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-09-02T08:11:37Z","modified":"2026-02-04T02:42:45.068919Z","updated_at":"2026-11-02T16:58:32.266854Z"},{"id":"SUSE-SU-2021:14848-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\n- CVE-2021-0089: Fixed Speculative Code Store Bypass (XSA-375) (bsc#1186433).\n- CVE-2021-20255: Fixed stack overflow via infinite recursion in eepro100 (bsc#1182654).\n- CVE-2021-28690: Fixed x86 TSX Async Abort protections not restored after S3 (XSA-377) (bsc#1186434).\n- CVE-2021-28692: Fixed inappropriate x86 IOMMU timeout detection / handling (XSA-373) (bsc#1186429).\n- CVE-2021-28697: Fixed grant table v2 status pages may remain accessible after de-allocation (XSA-379) (bsc#1189376).\n- CVE-2021-28698: Fixed long running loops in grant table handling. (XSA-380) (bsc#1189378).\n- CVE-2021-28701: Fixed race condition in XENMAPSPACE_grant_table handling (XSA-384) (bsc#1189632).\n- CVE-2021-28703: Fixed grant table v2 status pages may remain accessible after de-allocation (take two) (XSA-387) (bsc#1192555).\n- CVE-2021-28705, CVE-2021-28709: Fixed issues with partially successful P2M updates on x86 (XSA-389) (bsc#1192559).\n- CVE-2021-28706: Fixed guests may exceed their designated memory limit (XSA-385) (bsc#1192554).\n- CVE-2021-3527: Fixed unbounded stack allocation in usbredir (bsc#1186013).\n- CVE-2021-3592: Fixed invalid pointer initialization may lead to information disclosure in slirp (bootp) (bsc#1187369).\n- CVE-2021-3594: Fixed invalid pointer initialization may lead to information disclosure in slirp (udp) (bsc#1187378).\n- CVE-2021-3595: Fixed invalid pointer initialization may lead to information disclosure in slirp (tftp) (bsc#1187376).\n- CVE-2021-3682: Fixed free call on invalid pointer in usbredir bufp_alloc (bsc#1189150).\n- CVE-2021-3930: Fixed off-by-one error in mode_sense_page() in hw/scsi/scsi-disk.c (bsc#1192526).\n","status":"published","published":"2021-12-01T15:57:08Z","modified":"2025-05-02T04:30:58.855247Z","updated_at":"2026-11-02T15:53:49.138643Z"},{"id":"SUSE-SU-2021:2922-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nUpdate to Xen 4.13.3 general bug fix release (bsc#1027519).\n\nSecurity issues fixed:\n\n- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).\n\nOther issues fixed:\n\n- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)\n- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)\n- Fixed shell macro expansion in the spec file, so that ExecStart=\n  in xendomains-wait-disks.service is created correctly (bsc#1183877)\n- Upstream bug fixes (bsc#1027519)\n- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).\n- xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU during shutdown (bsc#1176189).\n- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-09-02T08:10:22Z","modified":"2026-02-04T04:04:04.043961Z","updated_at":"2026-11-02T15:53:49.605187Z"},{"id":"SUSE-SU-2021:2923-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nUpdate to Xen 4.13.3 general bug fix release (bsc#1027519).\n\nSecurity issues fixed:\n\n- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).\n\nOther issues fixed:\n\n- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)\n- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)\n- Fixed shell macro expansion in the spec file, so that ExecStart=\n  in xendomains-wait-disks.service is created correctly (bsc#1183877)\n- Upstream bug fixes (bsc#1027519)\n- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).\n- xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU during shutdown (bsc#1176189).\n- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).\n- Some long deprecated commands were finally removed in qemu6. Adjust libxl to use supported commands (bsc#1183243).\n- Update logrotate.conf, move global options into per-file sections to prevent globbering of global state (bsc#1187406).\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-09-02T08:11:36Z","modified":"2025-05-02T04:30:58.917642Z","updated_at":"2026-11-02T15:53:49.605187Z"},{"id":"SUSE-SU-2021:2924-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)\n- CVE-2021-20255: Fixed stack overflow via infinite recursion in eepro100 (bsc#1182654)\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).\n- CVE-2021-3592: slirp: invalid pointer initialization may lead to information disclosure (bootp)(bsc#1187369).\n- CVE-2021-3594: slirp: invalid pointer initialization may lead to information disclosure (udp)(bsc#1187378).\n- CVE-2021-3595: slirp: invalid pointer initialization may lead to information disclosure (tftp)(bsc#1187376).\n\nOther issues fixed:\n\n- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)\n- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)\n- Upstream bug fixes (bsc#1027519)\n\n- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).\n- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).\n- Fixed PVHVM SLES12 SP5 - NMI Watchdog CPU Stuck (bsc#1180846).\n- Core cannot be opened when using xl dump-core of VM with PTF (bsc#1183243)\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-09-02T08:12:49Z","modified":"2026-02-04T04:33:23.775608Z","updated_at":"2026-11-02T15:53:49.605187Z"},{"id":"SUSE-SU-2021:2925-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)\n\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).\n\nOther issues fixed:\n\n- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)\n- Upstream bug fixes (bsc#1027519)\n- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).\n- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).\n- Fixed PVHVM SLES12 SP5 - NMI Watchdog CPU Stuck (bsc#1180846).\n- Core cannot be opened when using xl dump-core of VM with PTF (bsc#1183243).\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-09-02T12:40:10Z","modified":"2026-02-04T02:13:33.615392Z","updated_at":"2026-11-02T15:53:49.605187Z"},{"id":"SUSE-SU-2021:2943-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429).\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434).\n\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-09-03T07:26:23Z","modified":"2026-02-04T03:59:51.547563Z","updated_at":"2026-11-02T15:53:49.605187Z"},{"id":"SUSE-SU-2021:2955-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)\n- CVE-2021-20255: Fixed stack overflow via infinite recursion in eepro100 (bsc#1182654)\n- CVE-2021-3592: slirp: invalid pointer initialization may lead to information disclosure (bootp)(bsc#1187369).\n- CVE-2021-3594: slirp: invalid pointer initialization may lead to information disclosure (udp)(bsc#1187378).\n- CVE-2021-3595: slirp: invalid pointer initialization may lead to information disclosure (tftp)(bsc#1187376).\n- CVE-2021-3308: Fixed IRQ vector leak on x86 (XSA-360)(bsc#1181254).\n\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-09-03T12:45:10Z","modified":"2026-02-04T04:37:20.894835Z","updated_at":"2026-11-02T15:53:49.605187Z"},{"id":"SUSE-SU-2021:2957-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\n- CVE-2021-3594: slirp: invalid pointer initialization may lead to information disclosure (udp)(bsc#1187378).\n- CVE-2021-3595: slirp: invalid pointer initialization may lead to information disclosure (tftp)(bsc#1187376).\n- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).\n- CVE-2021-20255: Fixed stack overflow via infinite recursion in eepro100 (bsc#1182654)\n- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)\n- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)\n- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-3592: slirp: invalid pointer initialization may lead to information disclosure (bootp)(bsc#1187369).\n\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-09-06T08:34:19Z","modified":"2026-02-04T02:45:06.621847Z","updated_at":"2026-11-02T15:53:49.605187Z"},{"id":"SUSE-SU-2021:3322-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\n- CVE-2021-28701: Fixed race condition in XENMAPSPACE_grant_table handling (XSA-384) (bsc#1189632).\n\n- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: Fixed IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).\n- CVE-2021-28697: Fixed grant table v2 status pages that may remain accessible after de-allocation (XSA-379)(bsc#1189376).\n- CVE-2021-28698: Fixed long running loops in grant table handling (XSA-380)(bsc#1189378).\n- CVE-2021-20255: Fixed eepro100 stack overflow via infinite recursion (bsc#1182654).\n- CVE-2021-3592: Fixed invalid pointer initialization may lead to information disclosure (bootp) (bsc#1187369).\n- CVE-2021-3594: Fixed invalid pointer initialization may lead to information disclosure (udp) (bsc#1187378).\n- CVE-2021-3595: Fixed invalid pointer initialization may lead to information disclosure (tftp) (bsc#1187376).\n- CVE-2021-28692: Fixed inappropriate x86 IOMMU timeout detection / handling (XSA-373)(bsc#1186429).\n- CVE-2021-0089: Fixed Speculative Code Store Bypass (XSA-375)(bsc#1186433).\n- CVE-2021-28690: Fixed x86 TSX Async Abort protections not restored after S3 (XSA-377)(bsc#1186434).\n\n- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).\n","status":"published","published":"2021-10-07T16:23:05Z","modified":"2026-02-04T04:06:51.259331Z","updated_at":"2026-11-02T15:53:49.605187Z"}]}}