CVE-2021-28699
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant...
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
5.5
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
- Record
CVE-2021-28699- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - CVSS 2.0
- 4.9 Medium
AV:L/AC:L/Au:N/C:N/I:N/A:C - Updated
- 2026-11-02
CVE List No score
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
- Record
CVE-2021-28699- Updated
- 2026-11-02
EUVDEUVD-2021-15356 No score
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
- Record
EUVD-2021-15356- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-gp69-2mv4-2f25
5.5
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant...
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
- Record
GHSA-gp69-2mv4-2f25- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVALPINE-CVE-2021-28699
5.5
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
- Record
ALPINE-CVE-2021-28699- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSV
5.5
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
- Record
CVE-2021-28699- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 11 moreShow less
OSVDEBIAN-CVE-2021-28699
5.5
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
- Record
DEBIAN-CVE-2021-28699- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2021-28699
5.5
inadequate grant-v2 status frames array bounds check The v2 grant table interface separates grant attributes from grant status. That is, when operating in this mode, a guest has two tables. As a result, guests also need to be able to retrieve the addresses that the new status tracking table can be accessed through. For 32-bit guests on x86, translation of requests has to occur because the interface structure layouts commonly differ between 32- and 64-bit. The translation of the request to obtain the frame numbers of the grant status table involves translating the resulting array of frame numbers. Since the space used to carry out the translation is limited, the translation layer tells the core function the capacity of the array within translation space. Unfortunately the core function then only enforces array bounds to be below 8 times the specified value, and would write past the available space if enough frame numbers needed storing.
- Record
UBUNTU-CVE-2021-28699- CVSS 3.1
- 5.5 Medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVopenSUSE-SU-2021:1236-1 No score
Security update for xen
This update for xen fixes the following issues:
Update to Xen 4.13.3 general bug fix release (bsc#1027519).
Security issues fixed:
- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).
Other issues fixed:
- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)
- Fixed shell macro expansion in the spec file, so that ExecStart= in xendomains-wait-disks.service is created correctly (bsc#1183877)
- Upstream bug fixes (bsc#1027519)
- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
- xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU during shutdown (bsc#1176189).
- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
This update was imported from the SUSE:SLE-15-SP2:Update update project.
- Record
openSUSE-SU-2021:1236-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2021:2923-1 No score
Security update for xen
This update for xen fixes the following issues:
Update to Xen 4.13.3 general bug fix release (bsc#1027519).
Security issues fixed:
- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).
Other issues fixed:
- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)
- Fixed shell macro expansion in the spec file, so that ExecStart= in xendomains-wait-disks.service is created correctly (bsc#1183877)
- Upstream bug fixes (bsc#1027519)
- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
- xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU during shutdown (bsc#1176189).
- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
- Some long deprecated commands were finally removed in qemu6. Adjust libxl to use supported commands (bsc#1183243).
- Update logrotate.conf, move global options into per-file sections to prevent globbering of global state (bsc#1187406).
- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
- Record
openSUSE-SU-2021:2923-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:2922-1 No score
Security update for xen
This update for xen fixes the following issues:
Update to Xen 4.13.3 general bug fix release (bsc#1027519).
Security issues fixed:
- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).
Other issues fixed:
- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)
- Fixed shell macro expansion in the spec file, so that ExecStart= in xendomains-wait-disks.service is created correctly (bsc#1183877)
- Upstream bug fixes (bsc#1027519)
- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
- xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU during shutdown (bsc#1176189).
- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
- Record
SUSE-SU-2021:2922-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:2923-1 No score
Security update for xen
This update for xen fixes the following issues:
Update to Xen 4.13.3 general bug fix release (bsc#1027519).
Security issues fixed:
- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).
Other issues fixed:
- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
- Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)
- Fixed shell macro expansion in the spec file, so that ExecStart= in xendomains-wait-disks.service is created correctly (bsc#1183877)
- Upstream bug fixes (bsc#1027519)
- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
- xl monitoring process exits during xl save -p|-c keep the monitoring process running to cleanup the domU during shutdown (bsc#1176189).
- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
- Some long deprecated commands were finally removed in qemu6. Adjust libxl to use supported commands (bsc#1183243).
- Update logrotate.conf, move global options into per-file sections to prevent globbering of global state (bsc#1187406).
- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
- Record
SUSE-SU-2021:2923-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:2924-1 No score
Security update for xen
This update for xen fixes the following issues:
Security issues fixed:
- CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
- CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
- CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
- CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
- CVE-2021-20255: Fixed stack overflow via infinite recursion in eepro100 (bsc#1182654)
- CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
- CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
- CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
- CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
- CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).
- CVE-2021-3592: slirp: invalid pointer initialization may lead to information disclosure (bootp)(bsc#1187369).
- CVE-2021-3594: slirp: invalid pointer initialization may lead to information disclosure (udp)(bsc#1187378).
- CVE-2021-3595: slirp: invalid pointer initialization may lead to information disclosure (tftp)(bsc#1187376).
Other issues fixed:
-
Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
-
Fixed an issue with xencommons, where file format expecations by fillup did not allign (bsc#1185682)
-
Upstream bug fixes (bsc#1027519)
-
Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
-
Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
-
Fixed PVHVM SLES12 SP5 - NMI Watchdog CPU Stuck (bsc#1180846).
-
Core cannot be opened when using xl dump-core of VM with PTF (bsc#1183243)
-
Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
- Record
SUSE-SU-2021:2924-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:2925-1 No score
Security update for xen
This update for xen fixes the following issues:
Security issues fixed:
-
CVE-2021-28693: xen/arm: Boot modules are not scrubbed (bsc#1186428)
-
CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
-
CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
-
CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
-
CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
-
CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
-
CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
-
CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
-
CVE-2021-28700: No memory limit for dom0less domUs (XSA-383)(bsc#1189381).
Other issues fixed:
- Fixed 'Panic on CPU 0: IO-APIC + timer doesn't work!' (bsc#1180491)
- Upstream bug fixes (bsc#1027519)
- Dom0 hangs when pinning CPUs for dom0 with HVM guest (bsc#1179246).
- Fixed Xen SLES11SP4 guest hangs on cluster (bsc#1188050).
- Fixed PVHVM SLES12 SP5 - NMI Watchdog CPU Stuck (bsc#1180846).
- Core cannot be opened when using xl dump-core of VM with PTF (bsc#1183243).
- Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
- Record
SUSE-SU-2021:2925-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:2943-1 No score
Security update for xen
This update for xen fixes the following issues:
-
CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
-
CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429).
-
CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433).
-
CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
-
CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
-
CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
-
CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434).
-
Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
- Record
SUSE-SU-2021:2943-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:2955-1 No score
Security update for xen
This update for xen fixes the following issues:
Security issues fixed:
-
CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
-
CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
-
CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
-
CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
-
CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
-
CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
-
CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
-
CVE-2021-20255: Fixed stack overflow via infinite recursion in eepro100 (bsc#1182654)
-
CVE-2021-3592: slirp: invalid pointer initialization may lead to information disclosure (bootp)(bsc#1187369).
-
CVE-2021-3594: slirp: invalid pointer initialization may lead to information disclosure (udp)(bsc#1187378).
-
CVE-2021-3595: slirp: invalid pointer initialization may lead to information disclosure (tftp)(bsc#1187376).
-
CVE-2021-3308: Fixed IRQ vector leak on x86 (XSA-360)(bsc#1181254).
-
Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
- Record
SUSE-SU-2021:2955-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:2957-1 No score
Security update for xen
This update for xen fixes the following issues:
-
CVE-2021-3594: slirp: invalid pointer initialization may lead to information disclosure (udp)(bsc#1187378).
-
CVE-2021-3595: slirp: invalid pointer initialization may lead to information disclosure (tftp)(bsc#1187376).
-
CVE-2021-28698: long running loops in grant table handling (XSA-380)(bsc#1189378).
-
CVE-2021-28699: inadequate grant-v2 status frames array bounds check (XSA-382)(bsc#1189380).
-
CVE-2021-20255: Fixed stack overflow via infinite recursion in eepro100 (bsc#1182654)
-
CVE-2021-28690: xen: x86: TSX Async Abort protections not restored after S3 (bsc#1186434)
-
CVE-2021-28692: xen: inappropriate x86 IOMMU timeout detection / handling (bsc#1186429)
-
CVE-2021-28694,CVE-2021-28695,CVE-2021-28696: IOMMU page mapping issues on x86 (XSA-378)(bsc#1189373).
-
CVE-2021-0089: xen: Speculative Code Store Bypass (bsc#1186433)
-
CVE-2021-28697: grant table v2 status pages may remain accessible after de-allocation (XSA-379)(bsc#1189376).
-
CVE-2021-3592: slirp: invalid pointer initialization may lead to information disclosure (bootp)(bsc#1187369).
-
Prevent superpage allocation in the LAPIC and ACPI_INFO range (bsc#1189882).
- Record
SUSE-SU-2021:2957-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
xenAlpine:v3.11 |
4.10.0 up to 4.13.3-r2 | 4.13.3-r2 |
xenAlpine:v3.12 |
4.10.0 up to 4.13.3-r2 | 4.13.3-r2 |
xenAlpine:v3.13 |
4.10.0 up to 4.14.2-r0 | 4.14.2-r0 |
xenAlpine:v3.14 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.15 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.16 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.17 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.18 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.19 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.20 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
Show 48 moreShow less
| Package | Affected | Fixed |
|---|---|---|
xenAlpine:v3.21 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.22 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.23 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenAlpine:v3.24 |
4.10.0 up to 4.15.0-r2 | 4.15.0-r2 |
xenDebian:12 |
before 4.14.3-1 | 4.14.3-1 |
xenDebian:13 |
before 4.14.3-1 | 4.14.3-1 |
xenDebian:14 |
before 4.14.3-1 | 4.14.3-1 |
xenDebian:11 From an advisory covering 8 CVEs |
before 4.14.3-1~deb11u1, plus listed versions 4.14.2+25-gb6a8c4f72d-2 |
4.14.3-1~deb11u1 |
xenSUSE:Linux Enterprise Module for Basesystem 15 SP2 From an advisory covering 11 CVEs |
before 4.13.3_02-3.34.1 | 4.13.3_02-3.34.1 |
xenSUSE:Linux Enterprise Module for Server Applications 15 SP2 From an advisory covering 11 CVEs |
before 4.13.3_02-3.34.1 | 4.13.3_02-3.34.1 |
xenSUSE:Linux Enterprise Micro 5.0 From an advisory covering 11 CVEs |
before 4.13.3_02-3.34.1 | 4.13.3_02-3.34.1 |
xenSUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 11 CVEs |
before 4.14.2_04-3.9.1 | 4.14.2_04-3.9.1 |
xenSUSE:Linux Enterprise Module for Server Applications 15 SP3 From an advisory covering 11 CVEs |
before 4.14.2_04-3.9.1 | 4.14.2_04-3.9.1 |
xenSUSE:Linux Enterprise Software Development Kit 12 SP5 From an advisory covering 15 CVEs |
before 4.12.4_12-3.49.1 | 4.12.4_12-3.49.1 |
xenSUSE:Linux Enterprise Server 12 SP5 From an advisory covering 15 CVEs |
before 4.12.4_12-3.49.1 | 4.12.4_12-3.49.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP5 From an advisory covering 15 CVEs |
before 4.12.4_12-3.49.1 | 4.12.4_12-3.49.1 |
xenSUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Linux Enterprise Server 15 SP1-BCL From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Linux Enterprise Server 15 SP1-LTSS From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 15 SP1 From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Manager Proxy 4.0 From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Manager Retail Branch Server 4.0 From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Manager Server 4.0 From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Enterprise Storage 6 From an advisory covering 11 CVEs |
before 4.12.4_12-3.52.1 | 4.12.4_12-3.52.1 |
xenSUSE:Linux Enterprise High Performance Computing 15-ESPOS From an advisory covering 9 CVEs |
before 4.10.4_26-3.61.1 | 4.10.4_26-3.61.1 |
xenSUSE:Linux Enterprise High Performance Computing 15-LTSS From an advisory covering 9 CVEs |
before 4.10.4_26-3.61.1 | 4.10.4_26-3.61.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 15 From an advisory covering 9 CVEs |
before 4.10.4_26-3.61.1 | 4.10.4_26-3.61.1 |
xenSUSE:OpenStack Cloud 9 From an advisory covering 14 CVEs |
before 4.11.4_20-2.60.1 | 4.11.4_20-2.60.1 |
xenSUSE:OpenStack Cloud Crowbar 9 From an advisory covering 14 CVEs |
before 4.11.4_20-2.60.1 | 4.11.4_20-2.60.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP4 From an advisory covering 14 CVEs |
before 4.11.4_20-2.60.1 | 4.11.4_20-2.60.1 |
xenSUSE:Linux Enterprise Server 12 SP4-LTSS From an advisory covering 14 CVEs |
before 4.11.4_20-2.60.1 | 4.11.4_20-2.60.1 |
xenSUSE:HPE Helion OpenStack 8 From an advisory covering 13 CVEs |
before 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 |
xenSUSE:OpenStack Cloud 8 From an advisory covering 13 CVEs |
before 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 |
xenSUSE:OpenStack Cloud Crowbar 8 From an advisory covering 13 CVEs |
before 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP3 From an advisory covering 13 CVEs |
before 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 |
xenSUSE:Linux Enterprise Server 12 SP3-LTSS From an advisory covering 13 CVEs |
before 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 |
xenSUSE:Linux Enterprise Server 12 SP3-BCL From an advisory covering 13 CVEs |
before 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 |
xenUbuntu:16.04:LTS |
All versions, plus listed versions 4.5.1-0ubuntu14.5.1-0ubuntu24.6.0-1ubuntu14.6.0-1ubuntu24.6.0-1ubuntu4 Show 7 moreShow less4.6.0-1ubuntu4.14.6.0-1ubuntu4.24.6.0-1ubuntu4.34.6.5-0ubuntu14.6.5-0ubuntu1.14.6.5-0ubuntu1.24.6.5-0ubuntu1.4 |
None known |
xenUbuntu:18.04:LTS |
All versions, plus listed versions 4.9.0-0ubuntu34.9.0-0ubuntu44.9.2-0ubuntu1 |
None known |
xenUbuntu:20.04:LTS |
All versions, plus listed versions 4.9.2-0ubuntu24.9.2-0ubuntu64.9.2-0ubuntu74.11.3+24-g14b62ab3e5-1ubuntu14.11.3+24-g14b62ab3e5-1ubuntu24.11.3+24-g14b62ab3e5-1ubuntu2.24.11.3+24-g14b62ab3e5-1ubuntu2.3 |
None known |
xenUbuntu:22.04:LTS |
All versions, plus listed versions 4.11.4+24-gddaaccbbab-1ubuntu24.16.0-1~ubuntu24.16.0-1~ubuntu2.1 |
None known |
xenUbuntu:24.04:LTS |
All versions, plus listed versions 4.17.2-14.17.2+55-g0b56bed864-14.17.2+76-ge1f9cb16e2-14.17.2+76-ge1f9cb16e2-1ubuntu14.17.3+10-g091466ba55-14.17.3+10-g091466ba55-1.1ubuntu24.17.3+10-g091466ba55-1.1ubuntu3 |
None known |
xenUbuntu:25.10 |
All versions, plus listed versions 4.20.0-1ubuntu14.20.0+68-g35cb38b222-1 |
None known |
xenUbuntu:26.10 |
All versions, plus listed versions 4.20.2+7-g1badcf5035-2build24.20.2+37-g61ff35323e-1ubuntu14.20.3+127-gc42374a105-1 |
None known |
xenUbuntu:26.04:LTS |
All versions, plus listed versions 4.20.0+68-g35cb38b222-14.20.2+7-g1badcf5035-24.20.2+7-g1badcf5035-2build2 |
None known |
xenopenSUSE:Leap 15.2 From an advisory covering 11 CVEs |
before 4.13.3_02-lp152.2.27.1 | 4.13.3_02-lp152.2.27.1 |
xenopenSUSE:Leap 15.3 From an advisory covering 11 CVEs |
before 4.14.2_04-3.9.1 | 4.14.2_04-3.9.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2021-28699 is a medium vulnerability (CVSS 5.5) in Debian Linux, published August 27, 2021. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.35%, the 29th percentile. Fixed in xen 4.13.3-r2.
References
xenbits.xenproject.org/xsa/advisory-382.txt
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LPRVHW4J4ZCPPOHZEWP5MOJT7XDGFFPJ
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FZCNPSRPGFCQRYE2BI4D4Q4SCE56ANV2
debian.org/security/2021/dsa-4977
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2VQCFAPBNGBBAOMJZG6QBREOG5IIDZID
security.gentoo.org/glsa/202208-23
Show 63 moreShow less
nvd.nist.gov/vuln/detail/CVE-2021-28699
lists.fedoraproject.org/archives/list/[email protected]/message/2VQCFAPBNGBBAOMJZG6QBREOG5IIDZID
lists.fedoraproject.org/archives/list/[email protected]/message/FZCNPSRPGFCQRYE2BI4D4Q4SCE56ANV2
lists.fedoraproject.org/archives/list/[email protected]/message/LPRVHW4J4ZCPPOHZEWP5MOJT7XDGFFPJ
github.com/advisories/GHSA-gp69-2mv4-2f25
security.alpinelinux.org/vuln/CVE-2021-28699
security-tracker.debian.org/tracker/CVE-2021-28699
suse.com/support/update/announcement/2021/suse-su-20212922-1
bugzilla.suse.com/1027519
bugzilla.suse.com/1137251
bugzilla.suse.com/1176189
bugzilla.suse.com/1179148
bugzilla.suse.com/1179246
bugzilla.suse.com/1180491
bugzilla.suse.com/1181989
bugzilla.suse.com/1183877
bugzilla.suse.com/1185682
bugzilla.suse.com/1186428
bugzilla.suse.com/1186429
bugzilla.suse.com/1186433
bugzilla.suse.com/1186434
bugzilla.suse.com/1188050
bugzilla.suse.com/1189373
bugzilla.suse.com/1189376
bugzilla.suse.com/1189378
bugzilla.suse.com/1189380
bugzilla.suse.com/1189381
bugzilla.suse.com/1189882
suse.com/security/cve/CVE-2021-0089
suse.com/security/cve/CVE-2021-28690
suse.com/security/cve/CVE-2021-28692
suse.com/security/cve/CVE-2021-28693
suse.com/security/cve/CVE-2021-28694
suse.com/security/cve/CVE-2021-28695
suse.com/security/cve/CVE-2021-28696
suse.com/security/cve/CVE-2021-28697
suse.com/security/cve/CVE-2021-28698
suse.com/security/cve/CVE-2021-28699
suse.com/security/cve/CVE-2021-28700
suse.com/support/update/announcement/2021/suse-su-20212923-1
bugzilla.suse.com/1183243
bugzilla.suse.com/1187406
suse.com/support/update/announcement/2021/suse-su-20212924-1
bugzilla.suse.com/1180846
bugzilla.suse.com/1182654
bugzilla.suse.com/1187369
bugzilla.suse.com/1187376
bugzilla.suse.com/1187378
suse.com/security/cve/CVE-2021-20255
suse.com/security/cve/CVE-2021-3592
suse.com/security/cve/CVE-2021-3594
suse.com/security/cve/CVE-2021-3595
suse.com/support/update/announcement/2021/suse-su-20212925-1
suse.com/support/update/announcement/2021/suse-su-20212943-1
suse.com/support/update/announcement/2021/suse-su-20212955-1
bugzilla.suse.com/1181254
suse.com/security/cve/CVE-2021-3308
suse.com/support/update/announcement/2021/suse-su-20212957-1
ubuntu.com/security/CVE-2021-28699
xenbits.xen.org/xsa/advisory-382.html
cve.org/CVERecord?id=CVE-2021-28699
lists.opensuse.org/archives/list/[email protected]/thread/VYJVCSKTOQY75TLGWH3HDYZAS33JTOTQ
lists.opensuse.org/archives/list/[email protected]/thread/JLC632KAG76ZVELO6CCNNSZVUXPDVXOQ