description: 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.
problem types: unknown
affected:
{
product: xen
vendor: Xen
versions:
lessThan: 4.12, status: unknown, version: unspecified, versionType: custom
lessThan: unspecified, status: affected, version: 4.13.x, versionType: custom
lessThan: unspecified, status: unaffected, version: next of xen-unstable, versionType: custom
}
{
product: xen
vendor: Xen
versions:
status: affected, version: 4.12.x
}
{
product: xen
vendor: Xen
versions:
status: affected, version: 4.11.x
}
metrics:
other: [
content: {'description': {'description_data': [{'lang': 'eng', 'value': 'After using S3 suspend at least once, CPU0 remains vulnerable to TAA.\n\nThis is an information leak.  For full details of the impact, see\nXSA-305.'}]}}
type: unknown
]