Every CVE Search/ Get API key

CVE-2021-28689

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest...

5.5 MediumFix available

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to virtualization. In AMD64, Xen had to use a different implementation approach, so Xen does not use ring 1 to support 64-bit guests. With the focus now being on 64-bit systems, and the availability of explicit hardware support for virtualization, fixing speculation issues in ring 1 is not a priority for processor companies. Indirect Branch Restricted Speculation (IBRS) is an architectural x86 extension put together to combat speculative execution sidechannel attacks, including Spectre v2. It was retrofitted in microcode to existing CPUs. For more details on Spectre v2, see: http://xenbits.xen.org/xsa/advisory-254.html However, IBRS does not architecturally protect ring 0 from predictions learnt in ring 1. For more details, see: https://software.intel.com/security-software-guidance/deep-dives/deep-dive-indirect-branch-restricted-speculation Similar situations may exist with other mitigations for other kinds of speculative execution attacks. The situation is quite likely to be similar for speculative execution attacks which have yet to be discovered, disclosed, or mitigated.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
None
Availability
None

Exploit likelihood

0.36%Down 0.4 points since Jun 12, 2021
90%50%10%1%

What each source reports

NVD Score used 5.5

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to virtualization. In AMD64, Xen had to use a different implementation approach, so Xen does not use ring 1 to support 64-bit guests. With the focus now being on 64-bit systems, and the availability of explicit hardware support for virtualization, fixing speculation issues in ring 1 is not a priority for processor companies. Indirect Branch Restricted Speculation (IBRS) is an architectural x86 extension put together to combat speculative execution sidechannel attacks, including Spectre v2. It was retrofitted in microcode to existing CPUs. For more details on Spectre v2, see: http://xenbits.xen.org/xsa/advisory-254.html However, IBRS does not architecturally protect ring 0 from predictions learnt in ring 1. For more details, see: https://software.intel.com/security-software-guidance/deep-dives/deep-dive-indirect-branch-restricted-speculation Similar situations may exist with other mitigations for other kinds of speculative execution attacks. The situation is quite likely to be similar for speculative execution attacks which have yet to be discovered, disclosed, or mitigated.

Record
CVE-2021-28689
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS 2.0
2.1 LowAV:L/AC:L/Au:N/C:P/I:N/A:N
Weakness
CWE-212
Updated
2026-11-02
CVE List No score

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to virtualization. In AMD64, Xen had to use a different implementation approach, so Xen does not use ring 1 to support 64-bit guests. With the focus now being on 64-bit systems, and the availability of explicit hardware support for virtualization, fixing speculation issues in ring 1 is not a priority for processor companies. Indirect Branch Restricted Speculation (IBRS) is an architectural x86 extension put together to combat speculative execution sidechannel attacks, including Spectre v2. It was retrofitted in microcode to existing CPUs. For more details on Spectre v2, see: http://xenbits.xen.org/xsa/advisory-254.html However, IBRS does not architecturally protect ring 0 from predictions learnt in ring 1. For more details, see: https://software.intel.com/security-software-guidance/deep-dives/deep-dive-indirect-branch-restricted-speculation Similar situations may exist with other mitigations for other kinds of speculative execution attacks. The situation is quite likely to be similar for speculative execution attacks which have yet to be discovered, disclosed, or mitigated.

Record
CVE-2021-28689
Updated
2026-11-02
EUVDEUVD-2021-15346 No score

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to virtualization. In AMD64, Xen had to use a different implementation approach, so Xen does not use ring 1 to support 64-bit guests. With the focus now being on 64-bit systems, and the availability of explicit hardware support for virtualization, fixing speculation issues in ring 1 is not a priority for processor companies. Indirect Branch Restricted Speculation (IBRS) is an architectural x86 extension put together to combat speculative execution sidechannel attacks, including Spectre v2. It was retrofitted in microcode to existing CPUs. For more details on Spectre v2, see: http://xenbits.xen.org/xsa/advisory-254.html However, IBRS does not architecturally protect ring 0 from predictions learnt in ring 1. For more details, see: https://software.intel.com/security-software-guidance/deep-dives/deep-dive-indirect-branch-restricted-speculation Similar situations may exist with other mitigations for other kinds of speculative execution attacks. The situation is quite likely to be similar for speculative execution attacks which have yet to be discovered, disclosed, or mitigated.

Record
EUVD-2021-15346
Updated
2026-11-03
GitHub AdvisoriesGHSA-45vh-fhgx-cr2p 5.5

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest...

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to virtualization. In AMD64, Xen had to use a different implementation approach, so Xen does not use ring 1 to support 64-bit guests. With the focus now being on 64-bit systems, and the availability of explicit hardware support for virtualization, fixing speculation issues in ring 1 is not a priority for processor companies. Indirect Branch Restricted Speculation (IBRS) is an architectural x86 extension put together to combat speculative execution sidechannel attacks, including Spectre v2. It was retrofitted in microcode to existing CPUs. For more details on Spectre v2, see: http://xenbits.xen.org/xsa/advisory-254.html However, IBRS does not architecturally protect ring 0 from predictions learnt in ring 1. For more details, see: https://software.intel.com/security-software-guidance/deep-dives/deep-dive-indirect-branch-restricted-speculation Similar situations may exist with other mitigations for other kinds of speculative execution attacks. The situation is quite likely to be similar for speculative execution attacks which have yet to be discovered, disclosed, or mitigated.

Record
GHSA-45vh-fhgx-cr2p
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness
CWE-119
Updated
2026-11-02
OSV 5.5

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to virtualization. In AMD64, Xen had to use a different implementation approach, so Xen does not use ring 1 to support 64-bit guests. With the focus now being on 64-bit systems, and the availability of explicit hardware support for virtualization, fixing speculation issues in ring 1 is not a priority for processor companies. Indirect Branch Restricted Speculation (IBRS) is an architectural x86 extension put together to combat speculative execution sidechannel attacks, including Spectre v2. It was retrofitted in microcode to existing CPUs. For more details on Spectre v2, see: http://xenbits.xen.org/xsa/advisory-254.html However, IBRS does not architecturally protect ring 0 from predictions learnt in ring 1. For more details, see: https://software.intel.com/security-software-guidance/deep-dives/deep-dive-indirect-branch-restricted-speculation Similar situations may exist with other mitigations for other kinds of speculative execution attacks. The situation is quite likely to be similar for speculative execution attacks which have yet to be discovered, disclosed, or mitigated.

Record
CVE-2021-28689
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Updated
2026-11-02
OSVDEBIAN-CVE-2021-28689 5.5

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to virtualization. In AMD64, Xen had to use a different implementation approach, so Xen does not use ring 1 to support 64-bit guests. With the focus now being on 64-bit systems, and the availability of explicit hardware support for virtualization, fixing speculation issues in ring 1 is not a priority for processor companies. Indirect Branch Restricted Speculation (IBRS) is an architectural x86 extension put together to combat speculative execution sidechannel attacks, including Spectre v2. It was retrofitted in microcode to existing CPUs. For more details on Spectre v2, see: http://xenbits.xen.org/xsa/advisory-254.html However, IBRS does not architecturally protect ring 0 from predictions learnt in ring 1. For more details, see: https://software.intel.com/security-software-guidance/deep-dives/deep-dive-indirect-branch-restricted-speculation Similar situations may exist with other mitigations for other kinds of speculative execution attacks. The situation is quite likely to be similar for speculative execution attacks which have yet to be discovered, disclosed, or mitigated.

Record
DEBIAN-CVE-2021-28689
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Updated
2026-11-02
Show 9 moreShow less
OSVUBUNTU-CVE-2021-28689 5.5

x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to virtualization. In AMD64, Xen had to use a different implementation approach, so Xen does not use ring 1 to support 64-bit guests. With the focus now being on 64-bit systems, and the availability of explicit hardware support for virtualization, fixing speculation issues in ring 1 is not a priority for processor companies. Indirect Branch Restricted Speculation (IBRS) is an architectural x86 extension put together to combat speculative execution sidechannel attacks, including Spectre v2. It was retrofitted in microcode to existing CPUs. For more details on Spectre v2, see: http://xenbits.xen.org/xsa/advisory-254.html However, IBRS does not architecturally protect ring 0 from predictions learnt in ring 1. For more details, see: https://software.intel.com/security-software-guidance/deep-dives/deep-dive-indirect-branch-restricted-speculation Similar situations may exist with other mitigations for other kinds of speculative execution attacks. The situation is quite likely to be similar for speculative execution attacks which have yet to be discovered, disclosed, or mitigated.

Record
UBUNTU-CVE-2021-28689
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Updated
2026-11-02
OSVSUSE-SU-2021:1648-1 No score

Security update for xen

This update for xen fixes the following issues:

Security issue fixed:

  • CVE-2021-28689: Fixed some x86 speculative vulnerabilities with bare (non-shim) 32-bit PV guests (XSA-370) (bsc#1185104)

  • Make sure xencommons is in a format as expected by fillup. (bsc#1185682)

    Each comment needs to be followed by an enabled key. Otherwise fillup will remove manually enabled key=value pairs, along with everything that looks like a stale comment, during next pkg update

  • A recent systemd update caused a regression in xenstored.service systemd now fails to track units that use systemd-notify (bsc#1183790)

  • Added a delay between the call to systemd-notify and the final exit of the wrapper script (bsc#1185021, bsc#1185196)

Record
SUSE-SU-2021:1648-1
Updated
2026-11-02
OSVSUSE-SU-2022:3665-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-26365: Fixed issue where Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (bsc#1200762).
  • CVE-2022-33740: Fixed issue where Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (bsc#1200762).
  • CVE-2022-33741: Fixed issue where data residing in the same 4K page as data shared with a backend was being accessible by such backend (bsc#1200762).
  • CVE-2022-33742: Fixed issue where data residing in the same 4K page as data shared with a backend was being accessible by such backend (bsc#1200762).
  • CVE-2022-33745: Fixed an insufficient TLB flush for x86 PV guests in shadow mode (bsc#1201394).
  • CVE-2021-28689: Fixed speculative vulnerabilities with bare (non-shim) 32-bit PV guests (bsc#1185104).

Bugfixes:

  • Fixed logic error in built-in default of max_event_channels (bsc#1167608, bsc#1201631).
  • Fixed issue where dom0 fails to boot with constrained vcpus and nodes (bsc#1197081).
  • Included upstream bugfixes (bsc#1027519).
Record
SUSE-SU-2022:3665-1
Updated
2026-11-02
OSVSUSE-SU-2022:3728-1 No score

Security update for xen

This update for xen fixes the following issues:

  • CVE-2022-26365: Fixed issue where Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (bsc#1200762).
  • CVE-2022-33740: Fixed issue where Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (bsc#1200762).
  • CVE-2022-33741: Fixed issue where data residing in the same 4K page as data shared with a backend was being accessible by such backend (bsc#1200762).
  • CVE-2022-33742: Fixed issue where data residing in the same 4K page as data shared with a backend was being accessible by such backend (bsc#1200762).
  • CVE-2022-33746: Fixed DoS due to excessively long P2M pool freeing (bsc#1203806).
  • CVE-2021-28689: Fixed speculative vulnerabilities with bare (non-shim) 32-bit PV guests (bsc#1185104).
  • CVE-2022-33748: Fixed DoS due to race in locking (bsc#1203807).
Record
SUSE-SU-2022:3728-1
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: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: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

Affected products

Affected packages

Affected packages
PackageAffectedFixed
xen
Debian:12
 All versions, plus listed versions
4.17.1+2-gb773c48e36-14.17.2+55-g0b56bed864-14.17.2+76-ge1f9cb16e2-14.17.2+76-ge1f9cb16e2-1~deb12u14.17.2-1
Show 20 moreShow less
4.17.3+10-g091466ba55-14.17.3+10-g091466ba55-1.14.17.3+10-g091466ba55-1.1~exp14.17.3+10-g091466ba55-1.1~exp24.17.3+10-g091466ba55-1~deb12u14.17.3+36-g54dacb5c02-14.17.5+23-ga4e5191dc0-14.17.5+23-ga4e5191dc0-1+deb12u14.17.5+72-g01140da4e8-14.19.0+14-g0918434e0f-1~exp14.19.1-14.19.1-1~exp14.19.1-1~exp44.20.0+68-g35cb38b222-14.20.0-14.20.0~rc2+1-gfcde5e0de8-1~exp14.20.2+37-g61ff35323e-14.20.2+7-g1badcf5035-14.20.2+7-g1badcf5035-24.20.3+127-gc42374a105-1
 None known
xen
Debian:13
 All versions, plus listed versions
4.20.0+68-g35cb38b222-14.20.2+37-g61ff35323e-0+deb13u14.20.2+37-g61ff35323e-14.20.2+7-g1badcf5035-0+deb13u14.20.2+7-g1badcf5035-14.20.2+7-g1badcf5035-24.20.3+127-gc42374a105-0+deb13u14.20.3+127-gc42374a105-1
 None known
xen
Debian:14
 All versions, plus listed versions
4.20.0+68-g35cb38b222-14.20.2+37-g61ff35323e-14.20.2+7-g1badcf5035-14.20.2+7-g1badcf5035-24.20.3+127-gc42374a105-1
 None known
xen
SUSE:OpenStack Cloud 9
 before 4.11.4_18-2.54.1
4.11.4_18-2.54.1
xen
SUSE:OpenStack Cloud Crowbar 9
 before 4.11.4_18-2.54.1
4.11.4_18-2.54.1
xen
SUSE:Linux Enterprise Server for SAP Applications 12 SP4
 before 4.11.4_18-2.54.1
4.11.4_18-2.54.1
xen
SUSE:Linux Enterprise Server 12 SP4-LTSS
 before 4.11.4_18-2.54.1
4.11.4_18-2.54.1
xen
SUSE:Linux Enterprise Module for Basesystem 15 SP3
From an advisory covering 8 CVEs
 before 4.14.5_06-150300.3.35.1
4.14.5_06-150300.3.35.1
xen
SUSE:Linux Enterprise Module for Server Applications 15 SP3
From an advisory covering 8 CVEs
 before 4.14.5_06-150300.3.35.1
4.14.5_06-150300.3.35.1
xen
SUSE:Linux Enterprise Micro 5.1
From an advisory covering 8 CVEs
 before 4.14.5_06-150300.3.35.1
4.14.5_06-150300.3.35.1
Show 37 moreShow less
Affected packages
PackageAffectedFixed
xen
SUSE:Linux Enterprise Micro 5.2
From an advisory covering 8 CVEs
 before 4.14.5_06-150300.3.35.1
4.14.5_06-150300.3.35.1
xen
openSUSE:Leap Micro 5.2
From an advisory covering 8 CVEs
 before 4.14.5_06-150300.3.35.1
4.14.5_06-150300.3.35.1
xen
openSUSE:Leap 15.3
From an advisory covering 8 CVEs
 before 4.14.5_06-150300.3.35.1
4.14.5_06-150300.3.35.1
xen
SUSE:Linux Enterprise Software Development Kit 12 SP5
From an advisory covering 7 CVEs
 before 4.12.4_28-3.77.1
4.12.4_28-3.77.1
xen
SUSE:Linux Enterprise Server 12 SP5
From an advisory covering 7 CVEs
 before 4.12.4_28-3.77.1
4.12.4_28-3.77.1
xen
SUSE:Linux Enterprise Server for SAP Applications 12 SP5
From an advisory covering 7 CVEs
 before 4.12.4_28-3.77.1
4.12.4_28-3.77.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 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 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
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
RecordedChangedSources
affected, facts
aliasesEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

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

In short

CVE-2021-28689 is a medium vulnerability (CVSS 5.5) in Xen, published May 19, 2021. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.36%, the 30th percentile. Fixed in xen 4.11.4_18-2.54.1.

References

Show 57 moreShow less
Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open