Количество 15
Количество 15
CVE-2022-23035
Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to assume them to be valid.
CVE-2022-23035
Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to assume them to be valid.
CVE-2022-23035
Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to assume them to be valid.
CVE-2022-23035
Insufficient cleanup of passed-through device IRQs The management of I ...
GHSA-5x5q-fcw5-7frv
Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to assume them to be valid.
SUSE-SU-2022:14886-1
Security update for xen
SUSE-SU-2022:0359-1
Security update for xen
SUSE-SU-2022:0342-1
Security update for xen
SUSE-SU-2022:0332-1
Security update for xen
SUSE-SU-2022:0331-1
Security update for xen
openSUSE-SU-2022:0333-1
Security update for xen
SUSE-SU-2022:0469-1
Security update for xen
SUSE-SU-2022:0468-1
Security update for xen
SUSE-SU-2022:0467-1
Security update for xen
SUSE-SU-2022:0333-1
Security update for xen
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2022-23035 Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to assume them to be valid. | CVSS3: 4.6 | 0% Низкий | около 4 лет назад |
 | CVE-2022-23035 Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to assume them to be valid. | CVSS3: 4.6 | 0% Низкий | около 4 лет назад |
 | CVE-2022-23035 Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to assume them to be valid. | CVSS3: 4.6 | 0% Низкий | около 4 лет назад |
| CVE-2022-23035 Insufficient cleanup of passed-through device IRQs The management of I ... | CVSS3: 4.6 | 0% Низкий | около 4 лет назад |
| GHSA-5x5q-fcw5-7frv Insufficient cleanup of passed-through device IRQs The management of IRQs associated with physical devices exposed to x86 HVM guests involves an iterative operation in particular when cleaning up after the guest's use of the device. In the case where an interrupt is not quiescent yet at the time this cleanup gets invoked, the cleanup attempt may be scheduled to be retried. When multiple interrupts are involved, this scheduling of a retry may get erroneously skipped. At the same time pointers may get cleared (resulting in a de-reference of NULL) and freed (resulting in a use-after-free), while other code would continue to assume them to be valid. | CVSS3: 4.6 | 0% Низкий | около 4 лет назад |
 | SUSE-SU-2022:14886-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:0359-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:0342-1 Security update for xen | около 4 лет назад | ||
| SUSE-SU-2022:0332-1 Security update for xen | около 4 лет назад | ||
| SUSE-SU-2022:0331-1 Security update for xen | около 4 лет назад | ||
| openSUSE-SU-2022:0333-1 Security update for xen | около 4 лет назад | ||
| SUSE-SU-2022:0469-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:0468-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:0467-1 Security update for xen | почти 4 года назад | ||
| SUSE-SU-2022:0333-1 Security update for xen | около 4 лет назад |
Уязвимостей на страницу