Skip to content

CVE-2022-42320

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore...

7.0 HighFix available

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Attack profile

How easy it is to exploit

Attack vector: Local
Complexity: High
Privileges needed: Low
User interaction: None

What an attacker can affect

Confidentiality: High
Integrity: High
Availability: High

Exploit likelihood

0.30%Down 0.6 points since Nov 2, 2022

What each source reports

NVD Score used 7.0

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Record: CVE-2022-42320
CVSS 3.1: 7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-459
Updated: 2026-11-02

CVE List No score

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Record: CVE-2022-42320
Updated: 2026-11-02

EUVDEUVD-2022-45395 No score

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Record: EUVD-2022-45395
Updated: 2026-11-03

GitHub AdvisoriesGHSA-p263-3p34-m82m 7.0

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore...

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Record: GHSA-p263-3p34-m82m
CVSS 3.1: 7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-459
Updated: 2026-11-02

OSVALPINE-CVE-2022-42320 7.0

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Record: ALPINE-CVE-2022-42320
CVSS 3.1: 7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-03

OSV 7.0

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Record: CVE-2022-42320
CVSS 3.1: 7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

Show 11 moreShow less

OSVDEBIAN-CVE-2022-42320 7.0

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Record: DEBIAN-CVE-2022-42320
CVSS 3.1: 7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-03

OSVUBUNTU-CVE-2022-42320 7.0

Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.

Record: UBUNTU-CVE-2022-42320
CVSS 3.1: 7.0 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated: 2026-11-02

OSVSUSE-SU-2022:3925-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-33746: Fixed DoS due to excessively long P2M pool freeing (bsc#1203806).
CVE-2022-33748: Fixed DoS due to race in locking (bsc#1203807).
CVE-2021-28689: Fixed speculative vulnerabilities with bare (non-shim) 32-bit PV guests (bsc#1185104).
CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42319: xen: Xenstore: Guests can cause Xenstore to not free temporary memory (bsc#1204488)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)
CVE-2022-42325,CVE-2022-42326: xen: Xenstore: Guests can create arbitrary number of nodes via transactions (bsc#1204496)
xen: Frontends vulnerable to backends (bsc#1193923)

Record: SUSE-SU-2022:3925-1
Updated: 2026-11-02

OSVSUSE-SU-2022:3928-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-33746: Fixed DoS due to excessively long P2M pool freeing (bsc#1203806).
CVE-2022-33748: Fixed DoS due to race in locking (bsc#1203807).
CVE-2021-28689: Fixed speculative vulnerabilities with bare (non-shim) 32-bit PV guests (bsc#1185104).
CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42319: xen: Xenstore: Guests can cause Xenstore to not free temporary memory (bsc#1204488)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)
CVE-2022-42325,CVE-2022-42326: xen: Xenstore: Guests can create arbitray number of nodes via transactions (bsc#1204496)
CVE-2022-26363,CVE-2022-26364: xen: Insufficient care with non-coherent mappings (bsc#1199966).
CVE-2022-26365,CVE-2022-33740,CVE-2022-33741,CVE-2022-33742: xen: Linux disk/nic frontends data leaks (bsc#1200762).
xen: Frontends vulnerable to backends (bsc#1193923).

Record: SUSE-SU-2022:3928-1
Updated: 2026-11-02

OSVSUSE-SU-2022:3947-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-33746: Fixed DoS due to excessively long P2M pool freeing (bsc#1203806)
CVE-2022-33748: Fixed DoS due to race in locking (bsc#1203807)
CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42319: xen: Xenstore: Guests can cause Xenstore to not free temporary memory (bsc#1204488)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)
CVE-2022-42325,CVE-2022-42326: xen: Xenstore: Guests can create arbitrary number of nodes via transactions (bsc#1204496)
xen: Frontends vulnerable to backends (bsc#1193923)

Record: SUSE-SU-2022:3947-1
Updated: 2026-11-02

OSVSUSE-SU-2022:3960-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42319: xen: Xenstore: Guests can cause Xenstore to not free temporary memory (bsc#1204488)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)
CVE-2022-42325,CVE-2022-42326: xen: Xenstore: Guests can create arbitrary number of nodes via transactions (bsc#1204496)

Record: SUSE-SU-2022:3960-1
Updated: 2026-11-02

OSVSUSE-SU-2022:3971-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-33746: Fixed DoS due to excessively long P2M pool freeing (bsc#1203806).
CVE-2022-33748: Fixed DoS due to race in locking (bsc#1203807).
CVE-2021-28689: Fixed speculative vulnerabilities with bare (non-shim) 32-bit PV guests (bsc#1185104).
CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42319: xen: Xenstore: Guests can cause Xenstore to not free temporary memory (bsc#1204488)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)
CVE-2022-42325,CVE-2022-42326: xen: Xenstore: Guests can create arbitrary number of nodes via transactions (bsc#1204496)
xen: Frontends vulnerable to backends (bsc#1193923).

Record: SUSE-SU-2022:3971-1
Updated: 2026-11-02

OSVSUSE-SU-2022:4007-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-33746: Fixed DoS due to excessively long P2M pool freeing (bsc#1203806).
CVE-2022-33748: Fixed DoS due to race in locking (bsc#1203807).
CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42319: xen: Xenstore: Guests can cause Xenstore to not free temporary memory (bsc#1204488)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)
CVE-2022-42325,CVE-2022-42326: xen: Xenstore: Guests can create arbitrary number of nodes via transactions (bsc#1204496)
xen: Frontends vulnerable to backends (bsc#1193923).

Record: SUSE-SU-2022:4007-1
Updated: 2026-11-02

OSVSUSE-SU-2022:4051-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-33746: Fixed DoS due to excessively long P2M pool freeing (bsc#1203806).
CVE-2022-33748: Fixed DoS due to race in locking (bsc#1203807).
CVE-2021-28689: Fixed speculative vulnerabilities with bare (non-shim) 32-bit PV guests (bsc#1185104).
CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)

Record: SUSE-SU-2022:4051-1
Updated: 2026-11-02

OSVSUSE-SU-2022:4241-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-33746: Fixed DoS due to excessively long P2M pool freeing (bsc#1203806).
CVE-2022-33748: Fixed DoS due to race in locking (bsc#1203807).
CVE-2021-28689: Fixed speculative vulnerabilities with bare (non-shim) 32-bit PV guests (bsc#1185104).
CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42319: xen: Xenstore: Guests can cause Xenstore to not free temporary memory (bsc#1204488)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)
CVE-2022-42325,CVE-2022-42326: xen: Xenstore: Guests can create arbitrary number of nodes via transactions (bsc#1204496)
xen: Frontends vulnerable to backends (bsc#1193923)

Record: SUSE-SU-2022:4241-1
Updated: 2026-11-02

OSVSUSE-SU-2022:4332-1 No score

Security update for xen

This update for xen fixes the following issues:

CVE-2022-42311, CVE-2022-42312, CVE-2022-42313, CVE-2022-42314, CVE-2022-42315, CVE-2022-42316, CVE-2022-42317, CVE-2022-42318: xen: Xenstore: Guests can let xenstored run out of memory (bsc#1204482)
CVE-2022-42309: xen: Xenstore: Guests can crash xenstored (bsc#1204485)
CVE-2022-42310: xen: Xenstore: Guests can create orphaned Xenstore nodes (bsc#1204487)
CVE-2022-42319: xen: Xenstore: Guests can cause Xenstore to not free temporary memory (bsc#1204488)
CVE-2022-42320: xen: Xenstore: Guests can get access to Xenstore nodes of deleted domains (bsc#1204489)
CVE-2022-42321: xen: Xenstore: Guests can crash xenstored via exhausting the stack (bsc#1204490)
CVE-2022-42322,CVE-2022-42323: xen: Xenstore: cooperating guests can create arbitrary numbers of nodes (bsc#1204494)
CVE-2022-42325,CVE-2022-42326: xen: Xenstore: Guests can create arbitrary number of nodes via transactions (bsc#1204496)
xen: Frontends vulnerable to backends (bsc#1193923)

Record: SUSE-SU-2022:4332-1
Updated: 2026-11-02

Affected products

Affected packages

Affected packages
Package	Affected	Fixed
`xen` Alpine:v3.14	before 4.15.4-r0	4.15.4-r0
`xen` Alpine:v3.15	before 4.15.4-r0	4.15.4-r0
`xen` Alpine:v3.16	before 4.16.3-r0	4.16.3-r0
`xen` Alpine:v3.17	before 4.16.3-r0	4.16.3-r0
`xen` Alpine:v3.18	before 4.17.0-r0	4.17.0-r0
`xen` Alpine:v3.19	before 4.17.0-r0	4.17.0-r0
`xen` Alpine:v3.20	before 4.17.0-r0	4.17.0-r0
`xen` Alpine:v3.21	before 4.17.0-r0	4.17.0-r0
`xen` Alpine:v3.22	before 4.17.0-r0	4.17.0-r0
`xen` Alpine:v3.23	before 4.17.0-r0	4.17.0-r0

Show 50 moreShow less

Affected packages
Package	Affected	Fixed
`xen` Alpine:v3.24	before 4.17.0-r0	4.17.0-r0
`xen` Debian:12	before 4.16.2+90-g0d39a6d1ae-1	4.16.2+90-g0d39a6d1ae-1
`xen` Debian:13	before 4.16.2+90-g0d39a6d1ae-1	4.16.2+90-g0d39a6d1ae-1
`xen` Debian:14	before 4.16.2+90-g0d39a6d1ae-1	4.16.2+90-g0d39a6d1ae-1
`xen` Debian:11 From an advisory covering 22 CVEs	before 4.14.5+86-g1c354767d5-1, plus listed versions 4.14.2+25-gb6a8c4f72d-24.14.3+32-g9de3671772-14.14.3+32-g9de3671772-1~deb11u14.14.3-14.14.3-1~deb11u14.14.4+74-gd7b22226b5-14.14.5+24-g87d90d511c-1	4.14.5+86-g1c354767d5-1
`xen` SUSE:Linux Enterprise High Performance Computing 15-ESPOS From an advisory covering 20 CVEs	before 4.10.4_40-150000.3.84.1	4.10.4_40-150000.3.84.1
`xen` SUSE:Linux Enterprise High Performance Computing 15-LTSS From an advisory covering 20 CVEs	before 4.10.4_40-150000.3.84.1	4.10.4_40-150000.3.84.1
`xen` SUSE:Linux Enterprise Server for SAP Applications 15 From an advisory covering 20 CVEs	before 4.10.4_40-150000.3.84.1	4.10.4_40-150000.3.84.1
`xen` SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS From an advisory covering 24 CVEs	before 4.12.4_30-150100.3.80.1	4.12.4_30-150100.3.80.1
`xen` SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS From an advisory covering 24 CVEs	before 4.12.4_30-150100.3.80.1	4.12.4_30-150100.3.80.1
`xen` SUSE:Linux Enterprise Server 15 SP1-BCL From an advisory covering 24 CVEs	before 4.12.4_30-150100.3.80.1	4.12.4_30-150100.3.80.1
`xen` SUSE:Linux Enterprise Server 15 SP1-LTSS From an advisory covering 24 CVEs	before 4.12.4_30-150100.3.80.1	4.12.4_30-150100.3.80.1
`xen` SUSE:Linux Enterprise Server for SAP Applications 15 SP1 From an advisory covering 24 CVEs	before 4.12.4_30-150100.3.80.1	4.12.4_30-150100.3.80.1
`xen` SUSE:Enterprise Storage 6 From an advisory covering 24 CVEs	before 4.12.4_30-150100.3.80.1	4.12.4_30-150100.3.80.1
`xen` SUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 20 CVEs	before 4.14.5_08-150300.3.40.1	4.14.5_08-150300.3.40.1
`xen` SUSE:Linux Enterprise Module for Server Applications 15 SP3 From an advisory covering 20 CVEs	before 4.14.5_08-150300.3.40.1	4.14.5_08-150300.3.40.1
`xen` SUSE:Linux Enterprise Micro 5.1 From an advisory covering 20 CVEs	before 4.14.5_08-150300.3.40.1	4.14.5_08-150300.3.40.1
`xen` SUSE:Linux Enterprise Micro 5.2 From an advisory covering 20 CVEs	before 4.14.5_08-150300.3.40.1	4.14.5_08-150300.3.40.1
`xen` openSUSE:Leap Micro 5.2 From an advisory covering 20 CVEs	before 4.14.5_08-150300.3.40.1	4.14.5_08-150300.3.40.1
`xen` openSUSE:Leap 15.3 From an advisory covering 20 CVEs	before 4.14.5_08-150300.3.40.1	4.14.5_08-150300.3.40.1
`xen` SUSE:Linux Enterprise Server 12 SP3-BCL From an advisory covering 17 CVEs	before 4.9.4_34-3.114.1	4.9.4_34-3.114.1
`xen` SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Linux Enterprise Server 15 SP2-BCL From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Linux Enterprise Server 15 SP2-LTSS From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Linux Enterprise Server for SAP Applications 15 SP2 From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Manager Proxy 4.1 From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Manager Retail Branch Server 4.1 From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Manager Server 4.1 From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Enterprise Storage 7 From an advisory covering 20 CVEs	before 4.13.4_16-150200.3.65.1	4.13.4_16-150200.3.65.1
`xen` SUSE:Linux Enterprise Micro 5.3 From an advisory covering 21 CVEs	before 4.16.2_08-150400.4.16.1	4.16.2_08-150400.4.16.1
`xen` SUSE:Linux Enterprise Module for Basesystem 15 SP4 From an advisory covering 21 CVEs	before 4.16.2_08-150400.4.16.1	4.16.2_08-150400.4.16.1
`xen` SUSE:Linux Enterprise Module for Server Applications 15 SP4 From an advisory covering 21 CVEs	before 4.16.2_08-150400.4.16.1	4.16.2_08-150400.4.16.1
`xen` openSUSE:Leap 15.4 From an advisory covering 21 CVEs	before 4.16.2_08-150400.4.16.1	4.16.2_08-150400.4.16.1
`xen` SUSE:Linux Enterprise Server 12 SP2-BCL From an advisory covering 17 CVEs	before 4.7.6_28-43.98.1	4.7.6_28-43.98.1
`xen` SUSE:OpenStack Cloud 9 From an advisory covering 20 CVEs	before 4.11.4_34-2.83.1	4.11.4_34-2.83.1
`xen` SUSE:OpenStack Cloud Crowbar 9 From an advisory covering 20 CVEs	before 4.11.4_34-2.83.1	4.11.4_34-2.83.1
`xen` SUSE:Linux Enterprise Server for SAP Applications 12 SP4 From an advisory covering 20 CVEs	before 4.11.4_34-2.83.1	4.11.4_34-2.83.1
`xen` SUSE:Linux Enterprise Server 12 SP4-LTSS From an advisory covering 20 CVEs	before 4.11.4_34-2.83.1	4.11.4_34-2.83.1
`xen` SUSE:Linux Enterprise Software Development Kit 12 SP5 From an advisory covering 17 CVEs	before 4.12.4_30-3.82.1	4.12.4_30-3.82.1
`xen` SUSE:Linux Enterprise Server 12 SP5 From an advisory covering 17 CVEs	before 4.12.4_30-3.82.1	4.12.4_30-3.82.1
`xen` SUSE:Linux Enterprise Server for SAP Applications 12 SP5 From an advisory covering 17 CVEs	before 4.12.4_30-3.82.1	4.12.4_30-3.82.1
`xen` Ubuntu: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 less 4.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
`xen` Ubuntu:18.04:LTS	All versions, plus listed versions 4.9.0-0ubuntu34.9.0-0ubuntu44.9.2-0ubuntu1	None known
`xen` Ubuntu: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
`xen` Ubuntu: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
`xen` Ubuntu: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
`xen` Ubuntu:25.10	All versions, plus listed versions 4.20.0-1ubuntu14.20.0+68-g35cb38b222-1	None known
`xen` Ubuntu: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
`xen` Ubuntu: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

History

History
Recorded	Changed	Sources
Nov 6, 2026	affected, facts	OSV
Nov 3, 2026	aliases	EUVD
Nov 2, 2026	first indexed	CVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2022-42320 is a high vulnerability (CVSS 7.0) in Xen, published November 1, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.30%, the 22nd percentile. Fixed in xen 4.15.4-r0.

References

Show 63 moreShow less