7.8
CWE
404
Advisory Published
Updated

CVE-2022-23033

First published: Tue Jan 25 2022(Updated: )

arm: guest_physmap_remove_page not removing the p2m mappings The functions to remove one or more entries from a guest p2m pagetable on Arm (p2m_remove_mapping, guest_physmap_remove_page, and p2m_set_entry with mfn set to INVALID_MFN) do not actually clear the pagetable entry if the entry doesn't have the valid bit set. It is possible to have a valid pagetable entry without the valid bit set when a guest operating system uses set/way cache maintenance instructions. For instance, a guest issuing a set/way cache maintenance instruction, then calling the XENMEM_decrease_reservation hypercall to give back memory pages to Xen, might be able to retain access to those pages even after Xen started reusing them for other purposes.

Credit: security@xen.org

Affected SoftwareAffected VersionHow to fix
debian/xen
4.11.4+107-gef32c7afa2-1
4.14.6-1
4.14.5+94-ge49571868d-1
4.17.1+2-gb773c48e36-1
4.17.2+55-g0b56bed864-1
Xen xen-unstable>=4.12.0
Fedora=34
Debian=11.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2022-23033?

    CVE-2022-23033 is considered a high severity vulnerability due to its potential impact on memory management within the Xen hypervisor.

  • How do I fix CVE-2022-23033?

    To fix CVE-2022-23033, it is recommended to upgrade to a patched version of the Xen hypervisor as specified in the relevant security advisories.

  • What are the affected versions of Xen for CVE-2022-23033?

    Affected versions of Xen for CVE-2022-23033 include versions prior to 4.12.0 as well as specific releases such as 4.11.4+107-gef32c7afa2-1 and 4.14.6-1.

  • What systems are impacted by CVE-2022-23033?

    CVE-2022-23033 impacts various systems running the Xen hypervisor, including Debian, Fedora, and their respective derivatives.

  • Is there a workaround for CVE-2022-23033?

    There is no official workaround for CVE-2022-23033; upgrading to a secure version is the recommended mitigation.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203