CVE-2019-19338
MediumA 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.
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness type
CWE-203CVE-2019-19338 is classified as CWE-203
See CWE-203 on MITRE CWE for full details on this weakness type.
References
The following references provide additional information about CVE-2019-19338 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
Third Party Advisory
-
PatchKernel patch commithttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-19338
-
PatchKernel patch commithttps://www.openwall.com/lists/oss-security/2019/12/10/3
Frequently asked questions
-
What is CVE-2019-19338?
CVE-2019-19338 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . CVE-2019-19338 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2019-19338?
CVE-2019-19338 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. -
Is there a patch available for CVE-2019-19338?
No patch is currently available for CVE-2019-19338. Monitor the NIST NVD and your Linux distribution's security advisories for updates.
-
Is CVE-2019-19338 actively exploited?
No — CVE-2019-19338 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.