Racy interactions between dirty vram tracking and paging log dirty hypercalls Activation of log dirty mode done by XEN_DMOP_track_dirty_vram (was 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 lack of mutually exclusive locking between both operations and can lead to entries being added in already freed slots, resulting in a memory leak.
NOTE: The following CVSS v3.0 metrics and score provided are preliminary and subject to review.
|Base Score:||5.6||Base Metrics:||AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H|
|Access Vector:||Local network||Attack Complexity:||High|
|Privileges Required:||Low||User Interaction:||None|
|Integrity Impact:||None||Availability Impact:||High|
|Oracle VM version 3 (xen)||OVMSA-2022-0012||2022-04-08|
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections please contact the Oracle Linux ULN team