Описание
lock order inversion in transitive grant copy handling As part of XSA-226 a missing cleanup call was inserted on an error handling path. While doing so, locking requirements were not paid attention to. As a result two cooperating guests granting each other transitive grants can cause locks to be acquired nested within one another, but in respectively opposite order. With suitable timing between the involved grant copy operations this may result in the locking up of a CPU.
Ссылки
- Mailing ListMitigationPatchThird Party Advisory
- MitigationPatchVendor Advisory
- Third Party Advisory
- MitigationPatchVendor Advisory
- Mailing ListMitigationPatchThird Party Advisory
- MitigationPatchVendor Advisory
- Third Party Advisory
- MitigationPatchVendor Advisory
Уязвимые конфигурации
Одно из
EPSS
5.6 Medium
CVSS3
Дефекты
Связанные уязвимости
lock order inversion in transitive grant copy handling As part of XSA-226 a missing cleanup call was inserted on an error handling path. While doing so, locking requirements were not paid attention to. As a result two cooperating guests granting each other transitive grants can cause locks to be acquired nested within one another, but in respectively opposite order. With suitable timing between the involved grant copy operations this may result in the locking up of a CPU.
lock order inversion in transitive grant copy handling As part of XSA- ...
lock order inversion in transitive grant copy handling As part of XSA-226 a missing cleanup call was inserted on an error handling path. While doing so, locking requirements were not paid attention to. As a result two cooperating guests granting each other transitive grants can cause locks to be acquired nested within one another, but in respectively opposite order. With suitable timing between the involved grant copy operations this may result in the locking up of a CPU.
EPSS
5.6 Medium
CVSS3