CVE-2022-26356
low-risk
Published 2022-04-05
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.
Do I need to act?
-
0.05% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.6/10
Medium
LOCAL
/ HIGH complexity
Affected Products (4)
Affected Vendors
References (14)
Third Party Advisory
https://www.debian.org/security/2022/dsa-5117
Third Party Advisory
https://xenbits.xenproject.org/xsa/advisory-397.txt
Third Party Advisory
https://www.debian.org/security/2022/dsa-5117
Third Party Advisory
https://xenbits.xenproject.org/xsa/advisory-397.txt
25
/ 100
low-risk
Severity
15/34 · Moderate
Exploitability
0/34 · Minimal
Exposure
10/34 · Low