CVE-2022-26356
- State
- Published
- Severity
- Not scored
- Published
- Apr 5, 2022
- Updated
- Aug 3, 2024
- Reserved
- Mar 2, 2022
Description
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.
Scores
The record has no CVSS score.
Weaknesses
The record names no weakness.
Affected Products
| Product | Versions |
|---|---|
xenXen |
|
References
- https://xenbits.xenproject.org/xsa/advisory-397.txt
- http://xenbits.xen.org/xsa/advisory-397.html
- [oss-security] 20220405 Xen Security Advisory 397 v2 (CVE-2022-26356) - Racy interactions between dirty vram tracking and paging log dirty hypercallsmailing-list
- DSA-5117vendor-advisory
- FEDORA-2022-dfbf7e2372vendor-advisory
- FEDORA-2022-64b2c02d29vendor-advisory
- GLSA-202402-07vendor-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.