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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: XEN
Published: 2022-01-25T13:36:25
Updated: 2024-08-03T03:28:42.940Z
Reserved: 2022-01-10T00:00:00
Link: CVE-2022-23033
Vulnrichment
No data.
NVD
Status : Modified
Published: 2022-01-25T14:15:08.967
Modified: 2023-11-07T03:44:01.610
Link: CVE-2022-23033
Redhat