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.
Published · last modified .
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.
EPSS exploit prediction
EPSS 0.002, 15.4th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Xen — versions consult Xen advisory XSA-397
- Debian Linux — versions 11.0
- Fedoraproject Fedora — versions 34, 35
Weakness classification (CWE)
References
- xenbits.xenproject.org/xsa/advisory-397.txt (Third Party Advisory)
- xenbits.xen.org/xsa/advisory-397.html (Patch, Third Party Advisory)
- [oss-security] 20220405 Xen Security Advisory 397 v2 (CVE-2022-26356) - Racy interactions between dirty vram tracking and paging log dirty hypercalls (mailing-list, Patch, Mailing List, Third Party Advisory)
- DSA-5117 (vendor-advisory, Third Party Advisory)
- FEDORA-2022-dfbf7e2372 (vendor-advisory)
- FEDORA-2022-64b2c02d29 (vendor-advisory)
- GLSA-202402-07 (vendor-advisory)