Количество 12
Количество 12
CVE-2022-26356
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.
CVE-2022-26356
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.
CVE-2022-26356
Racy interactions between dirty vram tracking and paging log dirty hyp ...
GHSA-wqf3-h5g7-w9q8
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.
SUSE-SU-2022:1506-1
Security update for xen
SUSE-SU-2022:1505-1
Security update for xen
SUSE-SU-2022:2158-1
Security update for xen
SUSE-SU-2022:1408-1
Security update for xen
SUSE-SU-2022:1359-1
Security update for xen
SUSE-SU-2022:1300-1
Security update for xen
SUSE-SU-2022:1285-1
Security update for xen
SUSE-SU-2022:1375-1
Security update for xen
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2022-26356 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. | CVSS3: 5.6 | 0% Низкий | почти 4 года назад |
 | CVE-2022-26356 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. | CVSS3: 5.6 | 0% Низкий | почти 4 года назад |
| CVE-2022-26356 Racy interactions between dirty vram tracking and paging log dirty hyp ... | CVSS3: 5.6 | 0% Низкий | почти 4 года назад |
| GHSA-wqf3-h5g7-w9q8 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. | CVSS3: 5.6 | 0% Низкий | почти 4 года назад |
 | SUSE-SU-2022:1506-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:1505-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:2158-1 Security update for xen | больше 3 лет назад | ||
| SUSE-SU-2022:1408-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:1359-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:1300-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:1285-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:1375-1 Security update for xen | почти 4 года назад |
Уязвимостей на страницу