Количество 16
Количество 16

BDU:2022-00335
Уязвимость кросплатформенного гипервизора Xen, связанная с небезопасным управлением привилегиями, позволяющая нарушителю получить доступ к конфиденциальным данным, а также вызвать отказ в обслуживании

CVE-2021-28692
inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.

CVE-2021-28692
inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.
CVE-2021-28692
inappropriate x86 IOMMU timeout detection / handling IOMMUs process co ...
GHSA-23j5-p74r-rvqm
inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded.

SUSE-SU-2021:2943-1
Security update for xen

openSUSE-SU-2021:2923-1
Security update for xen

openSUSE-SU-2021:1236-1
Security update for xen

SUSE-SU-2021:2925-1
Security update for xen

SUSE-SU-2021:2923-1
Security update for xen

SUSE-SU-2021:2922-1
Security update for xen

SUSE-SU-2021:3322-1
Security update for xen

SUSE-SU-2021:2957-1
Security update for xen

SUSE-SU-2021:2955-1
Security update for xen

SUSE-SU-2021:2924-1
Security update for xen

SUSE-SU-2021:14848-1
Security update for xen
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | BDU:2022-00335 Уязвимость кросплатформенного гипервизора Xen, связанная с небезопасным управлением привилегиями, позволяющая нарушителю получить доступ к конфиденциальным данным, а также вызвать отказ в обслуживании | CVSS3: 7.1 | 0% Низкий | около 4 лет назад |
![]() | CVE-2021-28692 inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded. | CVSS3: 7.1 | 0% Низкий | около 4 лет назад |
![]() | CVE-2021-28692 inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded. | CVSS3: 7.1 | 0% Низкий | около 4 лет назад |
CVE-2021-28692 inappropriate x86 IOMMU timeout detection / handling IOMMUs process co ... | CVSS3: 7.1 | 0% Низкий | около 4 лет назад | |
GHSA-23j5-p74r-rvqm inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded. | 0% Низкий | около 3 лет назад | ||
![]() | SUSE-SU-2021:2943-1 Security update for xen | почти 4 года назад | ||
![]() | openSUSE-SU-2021:2923-1 Security update for xen | почти 4 года назад | ||
![]() | openSUSE-SU-2021:1236-1 Security update for xen | почти 4 года назад | ||
![]() | SUSE-SU-2021:2925-1 Security update for xen | почти 4 года назад | ||
![]() | SUSE-SU-2021:2923-1 Security update for xen | почти 4 года назад | ||
![]() | SUSE-SU-2021:2922-1 Security update for xen | почти 4 года назад | ||
![]() | SUSE-SU-2021:3322-1 Security update for xen | почти 4 года назад | ||
![]() | SUSE-SU-2021:2957-1 Security update for xen | почти 4 года назад | ||
![]() | SUSE-SU-2021:2955-1 Security update for xen | почти 4 года назад | ||
![]() | SUSE-SU-2021:2924-1 Security update for xen | почти 4 года назад | ||
![]() | SUSE-SU-2021:14848-1 Security update for xen | больше 3 лет назад |
Уязвимостей на страницу