Covert Timing Channel Affecting perf package, versions <0:4.18.0-147.5.1.el8_1
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-RHEL8-PERF-3652747
- published 26 Jul 2021
- disclosed 18 Nov 2019
How to fix?
Upgrade RHEL:8 perf to version 0:4.18.0-147.5.1.el8_1 or higher.
This issue was patched in RHSA-2020:0339.
NVD Description
Note: Versions mentioned in the description apply only to the upstream perf package and not the perf package as distributed by RHEL.
See How to fix? for RHEL:8 relevant fixed versions and status.
A flaw was found in the fix for CVE-2019-11135, in the Linux upstream kernel versions before 5.5 where, the way Intel CPUs handle speculative execution of instructions when a TSX Asynchronous Abort (TAA) error occurs. When a guest is running on a host CPU affected by the TAA flaw (TAA_NO=0), but is not affected by the MDS issue (MDS_NO=1), the guest was to clear the affected buffers by using a VERW instruction mechanism. But when the MDS_NO=1 bit was exported to the guests, the guests did not use the VERW mechanism to clear the affected buffers. This issue affects guests running on Cascade Lake CPUs and requires that host has 'TSX' enabled. Confidentiality of data is the highest threat associated with this vulnerability.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-19338
- https://access.redhat.com/security/cve/CVE-2019-19338
- https://software.intel.com/security-software-guidance/insights/deep-dive-intel-transactional-synchronization-extensions-intel-tsx-asynchronous-abort
- https://www.openwall.com/lists/oss-security/2019/12/10/3
- https://access.redhat.com/errata/RHSA-2020:0339