CVE-2020-4788: Infoleak
A flaw was found in the Linux kernel. IBM Power9 processors can speculatively operate on data stored in the L1 cache before it has been completely validated. The attack has limited access to memory and is only able to access memory normally permissible to the execution context. The highest threat from this vulnerability is to data confidentiality.
Other sources
IBM Power9 (AIX 7.1, 7.2, and VIOS 3.1) processors could allow a local user to obtain sensitive information from the data in the L1 cache under extenuating circumstances. IBM X-Force ID: 189296.
IBM Power9 processors could allow a local user to obtain sensitive information from the data in the L1 cache under extenuating circumstances.
— IBM
The IBM Power9 processors can speculatively operate on data stored in the L1 cache before it has been completely validated. Unlike other attacks, the attack has limited access to memory and is only able to access memory normally permissable to the execution context. The Power9 systems implement hardware and microcode measures to mitigate unprotected data leakage. An attacker may however induce a condition where the operating system speculative execute instructions using data that the attacker controls. Measuring the timing access of the execution can allow an attacker with a local account to be able to infer memory contents.
— Red Hat
Affected Software
Remediation
Information
Patch Available
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2020-4788?
CVE-2020-4788 has a high severity rating due to its potential to allow data access through speculative execution vulnerabilities.
How do I fix CVE-2020-4788?
To fix CVE-2020-4788, apply the appropriate patches or updates provided by your operating system vendor.
Which systems are affected by CVE-2020-4788?
CVE-2020-4788 affects Linux kernel versions up to 0:4.18.0-372.9.1.el8 and certain versions of IBM AIX and VIOS.
Can CVE-2020-4788 be exploited remotely?
CVE-2020-4788 requires local access to the affected system for exploitation, limiting its remote attack surface.
Is there a workaround for CVE-2020-4788?
While a specific workaround for CVE-2020-4788 is not detailed, it is recommended to apply vendor patches and monitor security bulletins for updates.