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.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
History
No history.
Information
Published : 2022-04-05 13:15
Updated : 2024-11-21 06:53
NVD link : CVE-2022-26356
Mitre link : CVE-2022-26356
CVE.ORG link : CVE-2022-26356
JSON object : View
Products Affected
fedoraproject
- fedora
xen
- xen
debian
- debian_linux
CWE
CWE-667
Improper Locking