rpm package
opensuse/xen&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/xen&distro=openSUSE%20Tumbleweed
Vulnerabilities (300)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-102703 | Med | 4.4 | < 4.22.0_08-1.1 | 4.22.0_08-1.1 | Nov 4, 2026 | [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] A common access pattern is a batch of Grant Copy operations acting on adjacent address ranges in the same source or destination page. For performance | |
| CVE-2026-79611 | Med | 5.5 | < 4.22.0_06-1.1 | 4.22.0_06-1.1 | Oct 13, 2026 | For XSA-308 logic was introduced, as VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in. The resulting VMEntry failure i | |
| CVE-2026-79610 | Hig | 8.8 | < 4.22.0_06-1.1 | 4.22.0_06-1.1 | Oct 13, 2026 | XSA-501 was about issues with v1 -> v2 and v2 -> v1 changes racing certain other grant table operations. Sadly a v2 -> v1 -> v2 change has yet another effect which wasn't accounted for: During the first change, status pages would be freed. During the second change they would be | |
| CVE-2026-79609 | Hig | 8.8 | < 4.22.0_06-1.1 | 4.22.0_06-1.1 | Oct 13, 2026 | XPTI (Xen Page Table Isolation) was introduced to mitigate Meltdown (CVE-2017-5754, one aspect of XSA-254). This involves copying 64-bit PV guest page table entries from guest-chosen root page tables to the Xen- chosen one which is in actual use by hardware. To read the guest r | |
| CVE-2026-79608 | Cri | 9.8 | < 4.22.0_06-1.1 | 4.22.0_06-1.1 | Oct 13, 2026 | The workaround for XSA-433 (Zenbleed, CVE-2023-20593) was later re-worked to better integrate with other manipulations of the same MSR. In this rework an inverted conditional was introduced, resulting in the workaround to not be applied when needed and vice versa. For more detai | |
| CVE-2026-79607 | Med | 5.5 | < 4.22.0_06-1.1 | 4.22.0_06-1.1 | Oct 13, 2026 | During Xenstore live update the state record for a Xenstore watch with specified watch depth is written with two bytes missing. This results in an inconsistent state when reading the state back in the new Xenstore, causing a crash of Xenstore or wrong Xenstore data. | |
| CVE-2026-79603 | Med | 4.3 | < 4.22.0_04-1.1 | 4.22.0_04-1.1 | Sep 8, 2026 | x86 PV guests can free memory pages while still keeping a stale TLB entry pointing to them. A TLB flush is only issued by Xen (if needed) when the page is re-used. Since it's possible for the page to be scrubbed ahead of the TLB flush, there's a window where a PV guest can modi | |
| CVE-2026-79602 | Hig | 8.8 | < 4.22.0_04-1.1 | 4.22.0_04-1.1 | Sep 8, 2026 | A guest with a PCI device assigned that has at least a BAR on the IO port space can trigger a BUG() in Xen. | |
| CVE-2026-62437 | Med | 6.5 | < 4.22.0_04-1.1 | 4.22.0_04-1.1 | Sep 8, 2026 | When guests are terminated, various pieces of cleanup need carrying out. The cleaning up of PCI devices which were assigned to guests, and the associated removal of tracking structures for IRQs used by the devices occurs relatively early in the process. Unfortunately after that | |
| CVE-2026-62434 | Med | 5.3 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | A guest started with Populated on Demand enabled (PoD) can attempt to reclaim pages which aren't regular guest RAM. This can cause corruption of memory management state in Xen. | |
| CVE-2026-62433 | Hig | 7.3 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | Parts of the DM_OP handling code assumes the caller has provided the required number of buffers for the given operation without any checking being done. As a result, certain operations might access stack rubble as structures are possibly uninitialized. | |
| CVE-2026-62432 | Hig | 7.3 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | The EVTCHNOP_expand_array hypercall checks for whether FIFO event channels are enabled, but without holding the correct lock. It can race with EVTCHNOP_reset, resulting in dereferencing a NULL pointer. | |
| CVE-2026-62431 | Hig | 7.5 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | The logic to handle periodic Viridian STIMERs performs a division with an unchecked user-controlled divisor value, that can be set to zero to cause a #DE fault. | |
| CVE-2026-62430 | Hig | 7.5 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | Accesses to the CMOS memory contents are done using an indirect IO port pair. Therefore Xen needs to cache the guest chosen index, and one of the usages of the index didn't take the necessary locking to avoid concurrent changes. As a result, a guest could change the index after | |
| CVE-2026-62429 | Med | 6.5 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | Accessing the vNUMA configuration data of a guest is still possible when domain destruction has already started. The cleaning up of that configuration information is not synchronized with its retrieval by a device model controlling the guest. | |
| CVE-2026-62428 | Hig | 7.8 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | When grant-copy operations are processed, the respective grant may or may not already be in use by another operation (a mapping or another copy). For all copy operations the referenced guest frame is looked up. When another operation is already active for the grant (the grant is | |
| CVE-2026-62426 | Hig | 8.8 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] To manage the system, sysctl and platform operations are used by the control domain or a possible Xenstore domain. Some of these operations may not b | |
| CVE-2026-62423 | Med | 5.5 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The directory and Rock Ridge / SUSP walk in libfsimage's iso9660 driver derives several lengths directly from attacker-controlled on-disk fields witho | |
| CVE-2026-42494 | Med | 6.1 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The directory and Rock Ridge / SUSP walk in libfsimage's iso9660 driver derives several lengths directly from attacker-controlled on-disk fields witho | |
| CVE-2026-42493 | Hig | 7.5 | < 4.22.0_02-1.1 | 4.22.0_02-1.1 | Jul 28, 2026 | Addressing certain issues, in particular related to operations which may take excessively long and therefore would need preemption, has turned out overly costly. Since alternatives (HVM/PVH: HAP, PV: shim) are commonly available, the decision was to deprecate the functionality, |
- affected < 4.22.0_08-1.1fixed 4.22.0_08-1.1
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] A common access pattern is a batch of Grant Copy operations acting on adjacent address ranges in the same source or destination page. For performance
- affected < 4.22.0_06-1.1fixed 4.22.0_06-1.1
For XSA-308 logic was introduced, as VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in. The resulting VMEntry failure i
- affected < 4.22.0_06-1.1fixed 4.22.0_06-1.1
XSA-501 was about issues with v1 -> v2 and v2 -> v1 changes racing certain other grant table operations. Sadly a v2 -> v1 -> v2 change has yet another effect which wasn't accounted for: During the first change, status pages would be freed. During the second change they would be
- affected < 4.22.0_06-1.1fixed 4.22.0_06-1.1
XPTI (Xen Page Table Isolation) was introduced to mitigate Meltdown (CVE-2017-5754, one aspect of XSA-254). This involves copying 64-bit PV guest page table entries from guest-chosen root page tables to the Xen- chosen one which is in actual use by hardware. To read the guest r
- affected < 4.22.0_06-1.1fixed 4.22.0_06-1.1
The workaround for XSA-433 (Zenbleed, CVE-2023-20593) was later re-worked to better integrate with other manipulations of the same MSR. In this rework an inverted conditional was introduced, resulting in the workaround to not be applied when needed and vice versa. For more detai
- affected < 4.22.0_06-1.1fixed 4.22.0_06-1.1
During Xenstore live update the state record for a Xenstore watch with specified watch depth is written with two bytes missing. This results in an inconsistent state when reading the state back in the new Xenstore, causing a crash of Xenstore or wrong Xenstore data.
- affected < 4.22.0_04-1.1fixed 4.22.0_04-1.1
x86 PV guests can free memory pages while still keeping a stale TLB entry pointing to them. A TLB flush is only issued by Xen (if needed) when the page is re-used. Since it's possible for the page to be scrubbed ahead of the TLB flush, there's a window where a PV guest can modi
- affected < 4.22.0_04-1.1fixed 4.22.0_04-1.1
A guest with a PCI device assigned that has at least a BAR on the IO port space can trigger a BUG() in Xen.
- affected < 4.22.0_04-1.1fixed 4.22.0_04-1.1
When guests are terminated, various pieces of cleanup need carrying out. The cleaning up of PCI devices which were assigned to guests, and the associated removal of tracking structures for IRQs used by the devices occurs relatively early in the process. Unfortunately after that
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
A guest started with Populated on Demand enabled (PoD) can attempt to reclaim pages which aren't regular guest RAM. This can cause corruption of memory management state in Xen.
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
Parts of the DM_OP handling code assumes the caller has provided the required number of buffers for the given operation without any checking being done. As a result, certain operations might access stack rubble as structures are possibly uninitialized.
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
The EVTCHNOP_expand_array hypercall checks for whether FIFO event channels are enabled, but without holding the correct lock. It can race with EVTCHNOP_reset, resulting in dereferencing a NULL pointer.
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
The logic to handle periodic Viridian STIMERs performs a division with an unchecked user-controlled divisor value, that can be set to zero to cause a #DE fault.
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
Accesses to the CMOS memory contents are done using an indirect IO port pair. Therefore Xen needs to cache the guest chosen index, and one of the usages of the index didn't take the necessary locking to avoid concurrent changes. As a result, a guest could change the index after
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
Accessing the vNUMA configuration data of a guest is still possible when domain destruction has already started. The cleaning up of that configuration information is not synchronized with its retrieval by a device model controlling the guest.
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
When grant-copy operations are processed, the respective grant may or may not already be in use by another operation (a mapping or another copy). For all copy operations the referenced guest frame is looked up. When another operation is already active for the grant (the grant is
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] To manage the system, sysctl and platform operations are used by the control domain or a possible Xenstore domain. Some of these operations may not b
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The directory and Rock Ridge / SUSP walk in libfsimage's iso9660 driver derives several lengths directly from attacker-controlled on-disk fields witho
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The directory and Rock Ridge / SUSP walk in libfsimage's iso9660 driver derives several lengths directly from attacker-controlled on-disk fields witho
- affected < 4.22.0_02-1.1fixed 4.22.0_02-1.1
Addressing certain issues, in particular related to operations which may take excessively long and therefore would need preemption, has turned out overly costly. Since alternatives (HVM/PVH: HAP, PV: shim) are commonly available, the decision was to deprecate the functionality,
Page 1 of 15