CVE-2022-21125: Medium severity XEN Xen vulnerability

Published May 25, 2022
·
Updated

A flaw was found in hw. Incomplete cleanup of microarchitectural fill buffers on some Intel® Processors may allow an authenticated user to enable information disclosure via local access.

Other sources

Incomplete cleanup of microarchitectural fill buffers on some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.

Some processors do not properly clean up and remove temporary or supporting resources after they have been used.

References:

https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/technical-documentation/processor-mmio-stale-data-vulnerabilities.html

— Red Hat

Affected Software

41 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1160.76.1.rt56.1220.el7
0:3.10.0-1160.76.1.rt56.1220.el7
redhat/kernel<0:3.10.0-1160.76.1.el7
0:3.10.0-1160.76.1.el7
redhat/kernel-rt<0:4.18.0-372.26.1.rt7.183.el8_6
0:4.18.0-372.26.1.rt7.183.el8_6
redhat/kernel<0:4.18.0-372.26.1.el8_6
0:4.18.0-372.26.1.el8_6
redhat/kernel<0:4.18.0-147.76.1.el8_1
0:4.18.0-147.76.1.el8_1
redhat/kernel<0:4.18.0-193.93.1.el8_2
0:4.18.0-193.93.1.el8_2
redhat/kernel-rt<0:4.18.0-193.93.1.rt13.143.el8_2
0:4.18.0-193.93.1.rt13.143.el8_2
redhat/kernel-rt<0:4.18.0-305.65.1.rt7.137.el8_4
0:4.18.0-305.65.1.rt7.137.el8_4
redhat/kernel<0:4.18.0-305.65.1.el8_4
0:4.18.0-305.65.1.el8_4
redhat/kernel<0:5.14.0-162.6.1.el9_1
0:5.14.0-162.6.1.el9_1
redhat/kernel-rt<0:5.14.0-162.6.1.rt21.168.el9_1
0:5.14.0-162.6.1.rt21.168.el9_1
redhat/kernel<0:5.14.0-70.36.1.el9_0
0:5.14.0-70.36.1.el9_0
redhat/kernel-rt<0:5.14.0-70.36.1.rt21.108.el9_0
0:5.14.0-70.36.1.rt21.108.el9_0
XEN Xen
Fedoraproject Fedora=35
Fedoraproject Fedora=36
Intel Sgx Dcap Linux<1.14.100.3
Intel Sgx Dcap Windows<1.14.100.3
Intel Sgx Psw Windows<2.16.100.3
Intel Sgx Psw Linux<2.17.100.3
Intel Sgx Sdk Windows<2.16.100.3
Intel Sgx Sdk Linux<2.17.100.3
VMware ESXi=7.0
VMware ESXi=7.0-beta
VMware ESXi=7.0-update_1
VMware ESXi=7.0-update_1a
VMware ESXi=7.0-update_1b
VMware ESXi=7.0-update_1c
VMware ESXi=7.0-update_1d
VMware ESXi=7.0-update_2
VMware ESXi=7.0-update_2a
VMware ESXi=7.0-update_2c
VMware ESXi=7.0-update_2d
VMware ESXi=7.0-update_3c
VMware ESXi=7.0-update_3d
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Debian Debian Linux=11.0
debian/intel-microcode
3.20240813.1~deb11u13.20250211.1~deb11u13.20250211.1~deb12u13.20231114.1~deb12u13.20250211.1
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/xen
4.14.6-14.14.5+94-ge49571868d-14.17.5+23-ga4e5191dc0-1+deb12u14.17.5+23-ga4e5191dc0-14.20.0-14.20.0+68-g35cb38b222-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:3.10.0-1160.76.1.rt56.1220.el7
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:3.10.0-1160.76.1.el7
  3. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-372.26.1.rt7.183.el8_6
  4. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-372.26.1.el8_6
  5. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-147.76.1.el8_1
  6. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-193.93.1.el8_2
  7. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-193.93.1.rt13.143.el8_2
  8. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-305.65.1.rt7.137.el8_4
  9. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-305.65.1.el8_4
  10. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:5.14.0-162.6.1.el9_1
  11. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:5.14.0-162.6.1.rt21.168.el9_1
  12. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:5.14.0-70.36.1.el9_0
  13. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:5.14.0-70.36.1.rt21.108.el9_0
  14. Upgrade

    Upgrade debian/intel-microcode to a version that resolves this vulnerability.

    Fixed in 3.20240813.1~deb11u1Fixed in 3.20250211.1~deb11u1Fixed in 3.20250211.1~deb12u1Fixed in 3.20231114.1~deb12u1Fixed in 3.20250211.1
  15. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  16. Upgrade

    Upgrade debian/xen to a version that resolves this vulnerability.

    Fixed in 4.14.6-1Fixed in 4.14.5+94-ge49571868d-1Fixed in 4.17.5+23-ga4e5191dc0-1+deb12u1Fixed in 4.17.5+23-ga4e5191dc0-1Fixed in 4.20.0-1Fixed in 4.20.0+68-g35cb38b222-1

Event History

May 25, 2022
Data Sourced
via Red Hat·12:35 PM
DescriptionSeverityAffected Software
Jun 14, 2022
CVE Published
12:00 AM
Jun 15, 2022
CVE Published
via MITRE·08:01 PM
Data Sourced
via MITRE·08:01 PM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 12, 2024
Data Sourced
via Launchpad·12:05 AM
Description
May 2, 2025
Data Sourced
via Ubuntu·04:37 AM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2022-21125?

The severity of CVE-2022-21125 is considered moderate due to its potential for information disclosure.

2

How do I fix CVE-2022-21125?

To fix CVE-2022-21125, update to the appropriate patched kernel version as specified in the remediation details.

3

Which systems are affected by CVE-2022-21125?

CVE-2022-21125 affects certain Intel® Processors and various Linux kernel versions across different distributions.

4

What is the impact of CVE-2022-21125?

The impact of CVE-2022-21125 includes potential information disclosure to authenticated users via local access.

5

Can CVE-2022-21125 be exploited remotely?

No, CVE-2022-21125 requires local access to the system for exploitation.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203