Vulnerability in Xen
CVE-2022-26356
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.
EPSS: 0.002 (14.2th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 5.6 (Medium). Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H.
Affected products
- Xen — versions consult Xen advisory XSA-397
- Debian Debian_linux — versions 11.0
- Fedoraproject Fedora — versions 34, 35
Weakness classification (CWE)
References
- security@xen.org (Third Party Advisory)
- security@xen.org (Patch, Third Party Advisory)
- security@xen.org (mailing-list, Patch, Mailing List, Third Party Advisory)
- security@xen.org (vendor-advisory, Third Party Advisory)
- security@xen.org (vendor-advisory)
- security@xen.org (vendor-advisory)
- security@xen.org (vendor-advisory)
Frequently asked questions
- What is CVE-2022-26356?
- CVE-2022-26356 is a medium-severity vulnerability in Xen, classified under Improper Locking. CVSS score: 5.6/10. Published 2022-04-05.
- How severe is CVE-2022-26356?
- Medium severity. CVSS v3 base score is 5.6 out of 10.