VMX: VMentry failure with branch tracing and blocked states
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Xen | Xen | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Xen | Xen |
|
Vendor Workaround
Running only PV guests will avoid this vulnerability. Running HVM guests on only AMD or Hygon hardware will also avoid this vulnerability.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4818-1 | xen security update |
Debian DLA |
DLA-4881-1 | xen security update |
Debian DSA |
DSA-6571-1 | xen security update |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.161% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-399 CWE-467 |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-843 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Xen
Xen xen |
|
| Vendors & Products |
Xen
Xen xen |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-399 CWE-467 |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | VMX: VMentry failure with branch tracing and blocked states | |
| References |
|