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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade xen | Mar 26, 2024 | Apr 5, 2022 |
| Debian | — | Upgrade xen | Nov 4, 2022 | Apr 5, 2022 |
| Gentoo Linux | — | Upgrade app-emulation/xen. | Feb 5, 2024 | Apr 5, 2022 |
| Suse | — | Upgrade xen-libsUpgrade xen-toolsUpgrade xen-libs-32bitUpgrade xen-doc-htmlUpgrade xen-develUpgrade xen-tools-xendomains-wait-diskUpgrade xenUpgrade xen-tools-domU | Oct 26, 2022 | Apr 5, 2022 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub