PT-2022-17807

CVE-2022-26356

·

Published

2022-04-05

·

Updated

2024-06-15

Description by

CVSS 3.1
5.6
Medium
MetricsAV:L/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H
Name of the Vulnerable Software and Affected Versions Xen versions prior to 4.9
Description The issue arises from racy interactions between dirty vram tracking and paging log dirty hypercalls. Activation of log dirty mode done by XEN DMOP track dirty vram (previously named HVMOP track dirty vram before Xen 4.9) is racy with ongoing log dirty hypercalls. A suitably timed call to XEN DMOP track dirty vram can enable log dirty while another CPU is still in the process of tearing down the structures related to a previously enabled log dirty mode (XEN DOMCTL SHADOW OP OFF). This is due to the lack of mutually exclusive locking between both operations and can lead to entries being added in already freed slots, resulting in a memory leak.
Recommendations As a temporary workaround, consider disabling the XEN DMOP track dirty vram function until a patch is available. Restrict access to the log dirty mode to minimize the risk of exploitation. Avoid using the XEN DOMCTL SHADOW OP OFF operation in conjunction with XEN DMOP track dirty vram until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.
Impacts
Researchers
Vendors
Affected products
Weakness enumeration
Related identifiers
DSA-5117-1
OPENSUSE-SU-2022_1506-1
OPENSUSE-SU-2024:11979-1
SUSE-SU-2022:1285-1
SUSE-SU-2022:1300-1
SUSE-SU-2022:1359-1
SUSE-SU-2022:1375-1
SUSE-SU-2022:1408-1
SUSE-SU-2022:1505-1
SUSE-SU-2022_1505-1
SUSE-SU-2022:1506-1
SUSE-SU-2022_1506-1
SUSE-SU-2022:2158-1
SUSE-SU-2022_2158-1
Found an issue in the description? Have something to add? Feel free to write us 👾