rpm package
suse/xen&distro=SUSE Linux Enterprise Server 12 SP3-BCL
pkg:rpm/suse/xen&distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP3-BCL
Vulnerabilities (122)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-28708 | Hig | 8.8 | < 4.9.4_24-3.97.1 | 4.9.4_24-3.97.1 | Nov 24, 2021 | PoD operations on misaligned GFNs T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] x86 HVM and PVH guests may be started in populate-on-demand (PoD) mode, to provide a way for them to later easily hav | |
| CVE-2021-28707 | Hig | 8.8 | < 4.9.4_24-3.97.1 | 4.9.4_24-3.97.1 | Nov 24, 2021 | PoD operations on misaligned GFNs T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] x86 HVM and PVH guests may be started in populate-on-demand (PoD) mode, to provide a way for them to later easily hav | |
| CVE-2021-28706 | Hig | 8.6 | < 4.9.4_24-3.97.1 | 4.9.4_24-3.97.1 | Nov 24, 2021 | guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator established limit. This is a result of a calculation done with 32-bit precisio | |
| CVE-2021-28704 | Hig | 8.8 | < 4.9.4_24-3.97.1 | 4.9.4_24-3.97.1 | Nov 24, 2021 | PoD operations on misaligned GFNs T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] x86 HVM and PVH guests may be started in populate-on-demand (PoD) mode, to provide a way for them to later easily hav | |
| CVE-2021-28701 | Hig | 7.8 | < 4.9.4_22-3.94.2 | 4.9.4_22-3.94.2 | Sep 8, 2021 | Another race in XENMAPSPACE_grant_table handling Guests are permitted access to certain Xen-owned pages of memory. The majority of such pages remain allocated / associated with a guest for its entire lifetime. Grant table v2 status pages, however, are de-allocated when a guest sw | |
| CVE-2021-28699 | Med | 5.5 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Aug 27, 2021 | 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 tra | |
| CVE-2021-28698 | Med | 5.5 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Aug 27, 2021 | long running loops in grant table handling In order to properly monitor resource use, Xen maintains information on the grant mappings a domain may create to map grants offered by other domains. In the process of carrying out certain actions, Xen would iterate over all such entrie | |
| CVE-2021-28697 | Hig | 7.8 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Aug 27, 2021 | grant table v2 status pages may remain accessible after de-allocation Guest get permitted access to certain Xen-owned pages of memory. The majority of such pages remain allocated / associated with a guest for its entire lifetime. Grant table v2 status pages, however, get de-alloc | |
| CVE-2021-28696 | Med | 6.8 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Aug 27, 2021 | IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify regions of memory which should be left untranslated, which typically m | |
| CVE-2021-28695 | Med | 6.8 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Aug 27, 2021 | IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify regions of memory which should be left untranslated, which typically m | |
| CVE-2021-28694 | Med | 6.8 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Aug 27, 2021 | IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify regions of memory which should be left untranslated, which typically m | |
| CVE-2021-28692 | Hig | 7.1 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Jun 30, 2021 | 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, | |
| CVE-2021-28690 | Med | 6.5 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Jun 29, 2021 | x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details. Mitigating TAA by disabling TSX (the default and preferred option) requires s | |
| CVE-2021-3595 | Low | 3.8 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Jun 15, 2021 | An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the tftp_input() function and could occur while processing a udp packet that is smaller than the size of the 'tftp_t' structure. This issue may lead to out-of-boun | |
| CVE-2021-3594 | Low | 3.8 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Jun 15, 2021 | An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the udp_input() function and could occur while processing a udp packet that is smaller than the size of the 'udphdr' structure. This issue may lead to out-of-bound | |
| CVE-2021-3592 | Low | 3.8 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Jun 15, 2021 | An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the bootp_input() function and could occur while processing a udp packet that is smaller than the size of the 'bootp_t' structure. A malicious guest could use this | |
| CVE-2021-0089 | Med | 6.5 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Jun 9, 2021 | Observable response discrepancy in some Intel(R) Processors may allow an authorized user to potentially enable information disclosure via local access. | |
| CVE-2021-20255 | Med | 5.5 | < 4.9.4_20-3.91.1 | 4.9.4_20-3.91.1 | Mar 9, 2021 | A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator of QEMU. This issue occurs while processing controller commands due to a DMA reentry issue. This flaw allows a guest user or process to consume CPU cycles or crash the QEMU p | |
| CVE-2021-27379 | Hig | 7.8 | < 4.9.4_16-3.83.1 | 4.9.4_16-3.83.1 | Feb 18, 2021 | An issue was discovered in Xen through 4.11.x, allowing x86 Intel HVM guest OS users to achieve unintended read/write DMA access, and possibly cause a denial of service (host OS crash) or gain privileges. This occurs because a backport missed a flush, and thus IOMMU updates were | |
| CVE-2020-29484 | Med | 6.0 | < 4.9.4_16-3.80.1 | 4.9.4_16-3.80.1 | Dec 15, 2020 | An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering t |
- affected < 4.9.4_24-3.97.1fixed 4.9.4_24-3.97.1
PoD operations on misaligned GFNs T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] x86 HVM and PVH guests may be started in populate-on-demand (PoD) mode, to provide a way for them to later easily hav
- affected < 4.9.4_24-3.97.1fixed 4.9.4_24-3.97.1
PoD operations on misaligned GFNs T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] x86 HVM and PVH guests may be started in populate-on-demand (PoD) mode, to provide a way for them to later easily hav
- affected < 4.9.4_24-3.97.1fixed 4.9.4_24-3.97.1
guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator established limit. This is a result of a calculation done with 32-bit precisio
- affected < 4.9.4_24-3.97.1fixed 4.9.4_24-3.97.1
PoD operations on misaligned GFNs T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] x86 HVM and PVH guests may be started in populate-on-demand (PoD) mode, to provide a way for them to later easily hav
- affected < 4.9.4_22-3.94.2fixed 4.9.4_22-3.94.2
Another race in XENMAPSPACE_grant_table handling Guests are permitted access to certain Xen-owned pages of memory. The majority of such pages remain allocated / associated with a guest for its entire lifetime. Grant table v2 status pages, however, are de-allocated when a guest sw
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
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 tra
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
long running loops in grant table handling In order to properly monitor resource use, Xen maintains information on the grant mappings a domain may create to map grants offered by other domains. In the process of carrying out certain actions, Xen would iterate over all such entrie
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
grant table v2 status pages may remain accessible after de-allocation Guest get permitted access to certain Xen-owned pages of memory. The majority of such pages remain allocated / associated with a guest for its entire lifetime. Grant table v2 status pages, however, get de-alloc
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify regions of memory which should be left untranslated, which typically m
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify regions of memory which should be left untranslated, which typically m
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
IOMMU page mapping issues on x86 T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Both AMD and Intel allow ACPI tables to specify regions of memory which should be left untranslated, which typically m
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
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,
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details. Mitigating TAA by disabling TSX (the default and preferred option) requires s
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the tftp_input() function and could occur while processing a udp packet that is smaller than the size of the 'tftp_t' structure. This issue may lead to out-of-boun
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the udp_input() function and could occur while processing a udp packet that is smaller than the size of the 'udphdr' structure. This issue may lead to out-of-bound
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the bootp_input() function and could occur while processing a udp packet that is smaller than the size of the 'bootp_t' structure. A malicious guest could use this
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
Observable response discrepancy in some Intel(R) Processors may allow an authorized user to potentially enable information disclosure via local access.
- affected < 4.9.4_20-3.91.1fixed 4.9.4_20-3.91.1
A stack overflow via an infinite recursion vulnerability was found in the eepro100 i8255x device emulator of QEMU. This issue occurs while processing controller commands due to a DMA reentry issue. This flaw allows a guest user or process to consume CPU cycles or crash the QEMU p
- affected < 4.9.4_16-3.83.1fixed 4.9.4_16-3.83.1
An issue was discovered in Xen through 4.11.x, allowing x86 Intel HVM guest OS users to achieve unintended read/write DMA access, and possibly cause a denial of service (host OS crash) or gain privileges. This occurs because a backport missed a flush, and thus IOMMU updates were
- affected < 4.9.4_16-3.80.1fixed 4.9.4_16-3.80.1
An issue was discovered in Xen through 4.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering t
Page 3 of 7