For XSA-308 logic was introduced, as VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Steppi...

原文の説明

取得元が公開している説明をそのまま載せています (多くは英語)。

For XSA-308 logic was introduced, as VMX VMEntry checks do not like the
exact combination of state which occurs when #DB in intercepted, Single
Stepping is active, and blocked by STI/MovSS is active, despite this being
a legitimate state to be in. The resulting VMEntry failure is fatal to
the guest.

Sadly there is another special sub-case of the above, with branch tracing
enabled. In that case the prior adjustment would still cause a VMentry
failure, as before fatal to the guest.

出典: OSV.dev (Open Source Vulnerabilities) OSV

影響パッケージ

Alpine:v3.21 xen

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.6-r2"}]}]

Alpine:v3.22 xen

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.20.4-r2"}]}]

Alpine:v3.23 xen

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.20.4-r2"}]}]

Alpine:v3.24 xen

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.21.2-r2"}]}]

参照URL

advisory security.alpinelinux.org