https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 03:56:50 +0000 https://cve.radiocsirt.org/vuln/certfr-2022-avi-314 certfr-2022-avi-314 https://cve.radiocsirt.org/vuln/certfr-2022-avi-314 https://cve.radiocsirt.org/vuln/euvd-2026-14892 EUVD-2026-14892 https://cve.radiocsirt.org/vuln/euvd-2026-14892 https://cve.radiocsirt.org/vuln/fkie_cve-2022-26356 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-26356 https://cve.radiocsirt.org/vuln/ghsa-wqf3-h5g7-w9q8 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-wqf3-h5g7-w9q8 https://cve.radiocsirt.org/vuln/gsd-2022-26356 gsd-2022-26356 https://cve.radiocsirt.org/vuln/gsd-2022-26356 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11979-1 <p>xen-4.16.0_08-1.1 on GA media</p> <p>xen-4.16.0_08-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11979-1 https://cve.radiocsirt.org/vuln/suse-su-2022:1285-1 <p>Security update for xen</p> <p>Security update for xen</p> https://cve.radiocsirt.org/vuln/suse-su-2022:1285-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-26356 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen, Ubuntu:20.04:LTS: xen, Ubuntu:22.04:LTS: xen, Ubuntu:24.04:LTS: xen, Ubuntu:25.10: xen, Ubuntu:26.04:LTS: xen</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen, Ubuntu:20.04:LTS: xen, Ubuntu:22.04:LTS: xen, Ubuntu:24.04:LTS: xen, Ubuntu:25.10: xen, Ubuntu:26.04:LTS: xen</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-26356 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0453 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Citrix Systems Hypervisor, Citrix Systems XenServer und Xen ausnutzen, um seine Privilegien zu erhöhen, Informationen offenzulegen oder einen Denial of Service Zustand herbeizuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Citrix Systems Hypervisor, Citrix Systems XenServer und Xen ausnutzen, um seine Privilegien zu erhöhen, Informationen offenzulegen oder einen Denial of Service Zustand herbeizuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0453