Xen on x86
Approved changes feed: RSS · Atom
cpe:2.3:o:xen:xen:-:*:*:*:*:*:x86:*
part: o version: - update: *
| Vendor | Xen (f270236f-a538-5294-a46e-e4b9797d2f33) |
|---|---|
| Product | Xen (6d9b47a4-a58a-5de1-b3a1-7ee0dccc27e6) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | x86 |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/xen |
purl2cpe | 2026-08-13 06:19:39.897668 |
pkg:deb/ubuntu/xen |
purl2cpe | 2026-08-13 06:19:39.897670 |
pkg:github/mirage/xen |
purl2cpe | 2026-08-13 06:19:39.897671 |
pkg:github/xen-project/xen |
purl2cpe | 2026-08-13 06:19:39.897672 |
pkg:gitlab/xen-project/xen |
purl2cpe | 2026-08-13 06:19:39.897674 |
pkg:rpm/fedora/xen |
purl2cpe | 2026-08-13 06:19:39.897675 |
pkg:rpm/opensuse/xen |
purl2cpe | 2026-08-13 06:19:39.897676 |
pkg:xen/xen |
purl2cpe | 2026-08-13 06:19:39.897678 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-58150 |
vulnerable | 2026-06-08 07:35:17.337025 |
x86: buffer overrun with shadow paging + tracing
Shadow mode tracing code uses a set of per-CPU variables to avoid
cumbersome parameter passing. Some of these variables are written to
with guest controlled data, of guest controllable size. That size can
be larger than the variable, and bounding of the writes was missing.
Published: 2026-01-28T15:33:17.316Z
Updated: 2026-01-28T16:46:04.355Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-26361 |
vulnerable | 2026-06-08 05:41:51.356514 |
Details available
IOMMU: RMRR (VT-d) and unity map (AMD-Vi) handling issues T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR") for Intel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used for platform tasks such as legacy USB emulation. Since the precise purpose of these regions is unknown, once a device associated with such a region is active, the mappings of these regions need to remain continuouly accessible by the device. This requirement has been violated. Subsequent DMA or interrupts from the device may have unpredictable behaviour, ranging from IOMMU faults to memory corruption.
Published: 2022-04-05T00:00:00.000Z
Updated: 2024-08-03T05:03:32.802Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-26360 |
vulnerable | 2026-06-08 05:41:51.356049 |
Details available
IOMMU: RMRR (VT-d) and unity map (AMD-Vi) handling issues T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR") for Intel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used for platform tasks such as legacy USB emulation. Since the precise purpose of these regions is unknown, once a device associated with such a region is active, the mappings of these regions need to remain continuouly accessible by the device. This requirement has been violated. Subsequent DMA or interrupts from the device may have unpredictable behaviour, ranging from IOMMU faults to memory corruption.
Published: 2022-04-05T00:00:00.000Z
Updated: 2024-08-03T05:03:32.839Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-26359 |
vulnerable | 2026-06-08 05:41:51.355452 |
Details available
IOMMU: RMRR (VT-d) and unity map (AMD-Vi) handling issues T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR") for Intel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used for platform tasks such as legacy USB emulation. Since the precise purpose of these regions is unknown, once a device associated with such a region is active, the mappings of these regions need to remain continuouly accessible by the device. This requirement has been violated. Subsequent DMA or interrupts from the device may have unpredictable behaviour, ranging from IOMMU faults to memory corruption.
Published: 2022-04-05T00:00:00.000Z
Updated: 2024-08-03T05:03:32.395Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-26358 |
vulnerable | 2026-06-08 05:41:51.354850 |
Details available
IOMMU: RMRR (VT-d) and unity map (AMD-Vi) handling issues T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR") for Intel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used for platform tasks such as legacy USB emulation. Since the precise purpose of these regions is unknown, once a device associated with such a region is active, the mappings of these regions need to remain continuouly accessible by the device. This requirement has been violated. Subsequent DMA or interrupts from the device may have unpredictable behaviour, ranging from IOMMU faults to memory corruption.
Published: 2022-04-05T00:00:00.000Z
Updated: 2024-08-03T05:03:32.460Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-8897 |
vulnerable | 2026-06-08 05:12:06.669060 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.