CVE-2022-26356
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.
How to fix
- xen xen4.12.0, 4.14.0, 4.16.0 or later
- debian.org/security/2022/dsa-5117
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UHFSRVLM2JUCPDC2KGB7ETPQYJLCGBLD/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6ETPM2OVZZ6KOS2L7QO7SIW6XWT5OW3F/
- security.gentoo.org/glsa/202402-07
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| xen xen | 4.0.0 ≤ v < 4.12.0, 4.13.0 ≤ v < 4.14.0, 4.15.0 ≤ v < 4.16.0 | 4.12.0, 4.14.0, 4.16.0 |
| debian debian_linux | 11.0 | — |
| fedoraproject fedora | 34, 35 | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.