CVE-2023-31315: Code Injection
Improper validation in a model specific register (MSR) could allow a malicious program with ring0 access to modify SMM configuration while SMI lock is enabled, potentially leading to arbitrary code execution.
Other sources
Multiple AMD Processors could allow a local authenticated attacker to execute arbitrary code on the system, caused by improper validation in a model specific register (MSR). By modifying SMM configuration while SMI lock is enabled, an attacker could exploit this vulnerability to execute arbitrary code on the system.
— IBM
Researchers from IOActive have reported that it may be possible for an attacker with ring 0 access to modify the configuration of System Management Mode (SMM) even when SMM Lock is enabled.
Refer: https://www.amd.com/en/resources/product-security.html
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-31315?
CVE-2023-31315 is considered a high severity vulnerability due to its potential to enable arbitrary code execution.
How do I fix CVE-2023-31315?
To fix CVE-2023-31315, it is recommended to update the amd64-microcode package to versions 3.20240820.1~deb11u1, 3.20240820.1~deb12u1, or 3.20240820.1.
What type of access is required to exploit CVE-2023-31315?
Exploitation of CVE-2023-31315 requires ring0 access, typically granted to malicious programs running with high system privileges.
What is the impact of exploiting CVE-2023-31315?
Exploiting CVE-2023-31315 could allow an attacker to modify SMM configuration while the SMI lock is enabled, potentially leading to severe security breaches.
Who reported the CVE-2023-31315 vulnerability?
The CVE-2023-31315 vulnerability was reported by researchers from IOActive.