CVE-2022-26356

MEDIUM
5.6
CVSS Score
Published: April 5, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 04:35 AM UTC
3 products affected across 3 vendorsDebian LinuxFedoraXen

Using xen by Xen?

Get instant alerts when new vulnerabilities affect xen - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.6
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Xen· Xenwordpress-plugin
95%
4.0.0 ≤ v < 4.12.04.13.0 ≤ v < 4.14.04.15.0 ≤ v < 4.16.0
Affected range stops below 4.12.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.14.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.16.0, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in consult Xen advisory XSA-397 (unknown)

CVSS

Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card