CVEvulnerability

CVE-2022-26356

5.6 MEDIUM Published 2022-04-05 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2022-04-05
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.1 ([email protected])
5.6 MEDIUM — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H
CVSS 2.0 ([email protected])
4.0 MEDIUM — AV:L/AC:H/Au:N/C:N/I:N/A:C
Weaknesses
CWE-667

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.

Affected configurations

• xen xen (>= 4.0.0 < 4.12.0) • xen xen (>= 4.13.0 < 4.14.0) • xen xen (>= 4.15.0 < 4.16.0) • debian debian linux 11.0 • fedoraproject fedora 34 • fedoraproject fedora 35

Related

Weakness · CWE (1)

  • CWE-667 Improper Locking weakness

References