rpm package
suse/xen&distro=SUSE Linux Enterprise Server 11 SP4-LTSS
pkg:rpm/suse/xen&distro=SUSE%20Linux%20Enterprise%20Server%2011%20SP4-LTSS
Vulnerabilities (79)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-20255 | — | < 4.4.4_50-61.67.1 | 4.4.4_50-61.67.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-2020-29481 | — | < 4.4.4_48-61.61.1 | 4.4.4_48-61.61.1 | Dec 15, 2020 | An issue was discovered in Xen through 4.14.x. Access rights of Xenstore nodes are per domid. Unfortunately, existing granted access rights are not removed when a domain is being destroyed. This means that a new domain created with the same domid will inherit the access rights to | ||
| CVE-2020-29484 | — | < 4.4.4_48-61.61.1 | 4.4.4_48-61.61.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 | ||
| CVE-2020-29483 | — | < 4.4.4_48-61.61.1 | 4.4.4_48-61.61.1 | Dec 15, 2020 | An issue was discovered in Xen through 4.14.x. Xenstored and guests communicate via a shared memory page using a specific protocol. When a guest violates this protocol, xenstored will drop the connection to that guest. Unfortunately, this is done by just removing the guest from x | ||
| CVE-2020-29480 | — | < 4.4.4_48-61.61.1 | 4.4.4_48-61.61.1 | Dec 15, 2020 | An issue was discovered in Xen through 4.14.x. Neither xenstore implementation does any permission checks when reporting a xenstore watch event. A guest administrator can watch the root xenstored node, which will cause notifications for every created, modified, and deleted key. A | ||
| CVE-2020-29571 | — | < 4.4.4_48-61.61.1 | 4.4.4_48-61.61.1 | Dec 15, 2020 | An issue was discovered in Xen through 4.14.x. A bounds check common to most operation time functions specific to FIFO event channels depends on the CPU observing consistent state. While the producer side uses appropriately ordered writes, the consumer side isn't protected agains | ||
| CVE-2020-29570 | — | < 4.4.4_48-61.61.1 | 4.4.4_48-61.61.1 | Dec 15, 2020 | An issue was discovered in Xen through 4.14.x. Recording of the per-vCPU control block mapping maintained by Xen and that of pointers into the control block is reversed. The consumer assumes, seeing the former initialized, that the latter are also ready for use. Malicious or bugg | ||
| CVE-2020-29566 | — | < 4.4.4_48-61.61.1 | 4.4.4_48-61.61.1 | Dec 15, 2020 | An issue was discovered in Xen through 4.14.x. When they require assistance from the device model, x86 HVM guests must be temporarily de-scheduled. The device model will signal Xen when it has completed its operation, via an event channel, so that the relevant vCPU is rescheduled | ||
| CVE-2020-25723 | — | < 4.4.4_46-61.58.1 | 4.4.4_46-61.58.1 | Dec 2, 2020 | A reachable assertion issue was found in the USB EHCI emulation code of QEMU. It could occur while processing USB requests due to missing handling of DMA memory map failure. A malicious privileged user within the guest may abuse this flaw to send bogus USB requests and crash the | ||
| CVE-2020-29130 | — | < 4.4.4_48-61.61.1 | 4.4.4_48-61.61.1 | Nov 26, 2020 | slirp.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of header data even if that exceeds the total packet length. | ||
| CVE-2020-28368 | — | < 4.4.4_46-61.58.1 | 4.4.4_46-61.58.1 | Nov 10, 2020 | Xen through 4.14.x allows guest OS administrators to obtain sensitive information (such as AES keys from outside the guest) via a side-channel attack on a power/energy monitoring interface, aka a "Platypus" attack. NOTE: there is only one logically independent fix: to change the | ||
| CVE-2020-27670 | — | < 4.4.4_46-61.58.1 | 4.4.4_46-61.58.1 | Oct 22, 2020 | An issue was discovered in Xen through 4.14.x allowing x86 guest OS users to cause a denial of service (data corruption), cause a data leak, or possibly gain privileges because an AMD IOMMU page-table entry can be half-updated. | ||
| CVE-2020-27671 | — | < 4.4.4_46-61.58.1 | 4.4.4_46-61.58.1 | Oct 22, 2020 | An issue was discovered in Xen through 4.14.x allowing x86 HVM and PVH guest OS users to cause a denial of service (data corruption), cause a data leak, or possibly gain privileges because coalescing of per-page IOMMU TLB flushes is mishandled. | ||
| CVE-2020-27672 | — | < 4.4.4_46-61.58.1 | 4.4.4_46-61.58.1 | Oct 22, 2020 | An issue was discovered in Xen through 4.14.x allowing x86 guest OS users to cause a host OS denial of service, achieve data corruption, or possibly gain privileges by exploiting a race condition that leads to a use-after-free involving 2MiB and 1GiB superpages. | ||
| CVE-2020-27674 | — | < 4.4.4_46-61.58.1 | 4.4.4_46-61.58.1 | Oct 22, 2020 | An issue was discovered in Xen through 4.14.x allowing x86 PV guest OS users to gain guest OS privileges by modifying kernel memory contents, because invalidation of TLB entries is mishandled during use of an INVLPG-like attack technique. | ||
| CVE-2020-25603 | — | < 4.4.4_44-61.55.1 | 4.4.4_44-61.55.1 | Sep 23, 2020 | An issue was discovered in Xen through 4.14.x. There are missing memory barriers when accessing/allocating an event channel. Event channels control structures can be accessed lockless as long as the port is considered to be valid. Such a sequence is missing an appropriate memory | ||
| CVE-2020-25596 | — | < 4.4.4_44-61.55.1 | 4.4.4_44-61.55.1 | Sep 23, 2020 | An issue was discovered in Xen through 4.14.x. x86 PV guest kernels can experience denial of service via SYSENTER. The SYSENTER instruction leaves various state sanitization activities to software. One of Xen's sanitization paths injects a #GP fault, and incorrectly delivers it t | ||
| CVE-2020-25604 | — | < 4.4.4_44-61.55.1 | 4.4.4_44-61.55.1 | Sep 23, 2020 | An issue was discovered in Xen through 4.14.x. There is a race condition when migrating timers between x86 HVM vCPUs. When migrating timers of x86 HVM guests between its vCPUs, the locking model used allows for a second vCPU of the same guest (also operating on the timers) to rel | ||
| CVE-2020-25601 | — | < 4.4.4_44-61.55.1 | 4.4.4_44-61.55.1 | Sep 23, 2020 | An issue was discovered in Xen through 4.14.x. There is a lack of preemption in evtchn_reset() / evtchn_destroy(). In particular, the FIFO event channel model allows guests to have a large number of event channels active at a time. Closing all of these (when resetting all event c | ||
| CVE-2020-25600 | — | < 4.4.4_44-61.55.1 | 4.4.4_44-61.55.1 | Sep 23, 2020 | An issue was discovered in Xen through 4.14.x. Out of bounds event channels are available to 32-bit x86 domains. The so called 2-level event channel model imposes different limits on the number of usable event channels for 32-bit x86 domains vs 64-bit or Arm (either bitness) ones |
- CVE-2021-20255Mar 9, 2021affected < 4.4.4_50-61.67.1fixed 4.4.4_50-61.67.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
- CVE-2020-29481Dec 15, 2020affected < 4.4.4_48-61.61.1fixed 4.4.4_48-61.61.1
An issue was discovered in Xen through 4.14.x. Access rights of Xenstore nodes are per domid. Unfortunately, existing granted access rights are not removed when a domain is being destroyed. This means that a new domain created with the same domid will inherit the access rights to
- CVE-2020-29484Dec 15, 2020affected < 4.4.4_48-61.61.1fixed 4.4.4_48-61.61.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
- CVE-2020-29483Dec 15, 2020affected < 4.4.4_48-61.61.1fixed 4.4.4_48-61.61.1
An issue was discovered in Xen through 4.14.x. Xenstored and guests communicate via a shared memory page using a specific protocol. When a guest violates this protocol, xenstored will drop the connection to that guest. Unfortunately, this is done by just removing the guest from x
- CVE-2020-29480Dec 15, 2020affected < 4.4.4_48-61.61.1fixed 4.4.4_48-61.61.1
An issue was discovered in Xen through 4.14.x. Neither xenstore implementation does any permission checks when reporting a xenstore watch event. A guest administrator can watch the root xenstored node, which will cause notifications for every created, modified, and deleted key. A
- CVE-2020-29571Dec 15, 2020affected < 4.4.4_48-61.61.1fixed 4.4.4_48-61.61.1
An issue was discovered in Xen through 4.14.x. A bounds check common to most operation time functions specific to FIFO event channels depends on the CPU observing consistent state. While the producer side uses appropriately ordered writes, the consumer side isn't protected agains
- CVE-2020-29570Dec 15, 2020affected < 4.4.4_48-61.61.1fixed 4.4.4_48-61.61.1
An issue was discovered in Xen through 4.14.x. Recording of the per-vCPU control block mapping maintained by Xen and that of pointers into the control block is reversed. The consumer assumes, seeing the former initialized, that the latter are also ready for use. Malicious or bugg
- CVE-2020-29566Dec 15, 2020affected < 4.4.4_48-61.61.1fixed 4.4.4_48-61.61.1
An issue was discovered in Xen through 4.14.x. When they require assistance from the device model, x86 HVM guests must be temporarily de-scheduled. The device model will signal Xen when it has completed its operation, via an event channel, so that the relevant vCPU is rescheduled
- CVE-2020-25723Dec 2, 2020affected < 4.4.4_46-61.58.1fixed 4.4.4_46-61.58.1
A reachable assertion issue was found in the USB EHCI emulation code of QEMU. It could occur while processing USB requests due to missing handling of DMA memory map failure. A malicious privileged user within the guest may abuse this flaw to send bogus USB requests and crash the
- CVE-2020-29130Nov 26, 2020affected < 4.4.4_48-61.61.1fixed 4.4.4_48-61.61.1
slirp.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of header data even if that exceeds the total packet length.
- CVE-2020-28368Nov 10, 2020affected < 4.4.4_46-61.58.1fixed 4.4.4_46-61.58.1
Xen through 4.14.x allows guest OS administrators to obtain sensitive information (such as AES keys from outside the guest) via a side-channel attack on a power/energy monitoring interface, aka a "Platypus" attack. NOTE: there is only one logically independent fix: to change the
- CVE-2020-27670Oct 22, 2020affected < 4.4.4_46-61.58.1fixed 4.4.4_46-61.58.1
An issue was discovered in Xen through 4.14.x allowing x86 guest OS users to cause a denial of service (data corruption), cause a data leak, or possibly gain privileges because an AMD IOMMU page-table entry can be half-updated.
- CVE-2020-27671Oct 22, 2020affected < 4.4.4_46-61.58.1fixed 4.4.4_46-61.58.1
An issue was discovered in Xen through 4.14.x allowing x86 HVM and PVH guest OS users to cause a denial of service (data corruption), cause a data leak, or possibly gain privileges because coalescing of per-page IOMMU TLB flushes is mishandled.
- CVE-2020-27672Oct 22, 2020affected < 4.4.4_46-61.58.1fixed 4.4.4_46-61.58.1
An issue was discovered in Xen through 4.14.x allowing x86 guest OS users to cause a host OS denial of service, achieve data corruption, or possibly gain privileges by exploiting a race condition that leads to a use-after-free involving 2MiB and 1GiB superpages.
- CVE-2020-27674Oct 22, 2020affected < 4.4.4_46-61.58.1fixed 4.4.4_46-61.58.1
An issue was discovered in Xen through 4.14.x allowing x86 PV guest OS users to gain guest OS privileges by modifying kernel memory contents, because invalidation of TLB entries is mishandled during use of an INVLPG-like attack technique.
- CVE-2020-25603Sep 23, 2020affected < 4.4.4_44-61.55.1fixed 4.4.4_44-61.55.1
An issue was discovered in Xen through 4.14.x. There are missing memory barriers when accessing/allocating an event channel. Event channels control structures can be accessed lockless as long as the port is considered to be valid. Such a sequence is missing an appropriate memory
- CVE-2020-25596Sep 23, 2020affected < 4.4.4_44-61.55.1fixed 4.4.4_44-61.55.1
An issue was discovered in Xen through 4.14.x. x86 PV guest kernels can experience denial of service via SYSENTER. The SYSENTER instruction leaves various state sanitization activities to software. One of Xen's sanitization paths injects a #GP fault, and incorrectly delivers it t
- CVE-2020-25604Sep 23, 2020affected < 4.4.4_44-61.55.1fixed 4.4.4_44-61.55.1
An issue was discovered in Xen through 4.14.x. There is a race condition when migrating timers between x86 HVM vCPUs. When migrating timers of x86 HVM guests between its vCPUs, the locking model used allows for a second vCPU of the same guest (also operating on the timers) to rel
- CVE-2020-25601Sep 23, 2020affected < 4.4.4_44-61.55.1fixed 4.4.4_44-61.55.1
An issue was discovered in Xen through 4.14.x. There is a lack of preemption in evtchn_reset() / evtchn_destroy(). In particular, the FIFO event channel model allows guests to have a large number of event channels active at a time. Closing all of these (when resetting all event c
- CVE-2020-25600Sep 23, 2020affected < 4.4.4_44-61.55.1fixed 4.4.4_44-61.55.1
An issue was discovered in Xen through 4.14.x. Out of bounds event channels are available to 32-bit x86 domains. The so called 2-level event channel model imposes different limits on the number of usable event channels for 32-bit x86 domains vs 64-bit or Arm (either bitness) ones
Page 2 of 4