x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort speculative security…
xen
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Xen xen |
|
|
| Xen xen |
| No fix yet |
| Xen xen |
| No fix yet |
xen
| Product | Affected | Fixed in |
|---|---|---|
| Xen xen |
|
|
| Xen xen |
| No fix yet |
| Xen xen |
| No fix yet |
x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details. Mitigating TAA by disabling TSX (the default and preferred option) requires selecting a non-default setting in MSR_TSX_CTRL. This setting isn't restored after S3 suspend.
From the CVE record · XEN
Xen does not restore the MSR_TSX_CTRL setting that disables TSX after S3 suspend. This can leave systems exposed to the TSX Async Abort speculative security vulnerability after resume. The input does not specify attacker access or user-interaction requirements.
Engineers running Xen on x86 systems that use S3 suspend should check their installations; affected versions are not specified.