CVE-2023-53438 Details
Description
In the Linux kernel, the following vulnerability has been resolved: x86/MCE: Always save CS register on AMD Zen IF Poison errors The Instruction Fetch (IF) units on current AMD Zen-based systems do not guarantee a synchronous #MC is delivered for poison consumption errors. Therefore, MCG_STATUS[EIPV|RIPV] will not be set. However, the microarchitecture does guarantee that the exception is delivered within the same context. In other words, the exact rIP is not known, but the context is known to not have changed. There is no architecturally-defined method to determine this behavior. The Code Segment (CS) register is always valid on such IF unit poison errors regardless of the value of MCG_STATUS[EIPV|RIPV]. Add a quirk to save the CS register for poison consumption from the IF unit banks. This is needed to properly determine the context of the error. Otherwise, the severity grading function will assume the context is IN_KERNEL due to the m->cs value being 0 (the initialized value). This leads to unnecessary kernel panics on data poison errors due to the kernel believing the poison consumption occurred in kernel context.
A vulnerability exists in the Linux kernel's handling of poison consumption errors from the Instruction Fetch (IF) units on AMD Zen-based systems. These errors do not reliably trigger a synchronous Machine Check (#MC) exception, resulting in the absence of crucial context information. Although the exact instruction pointer (rIP) cannot be determined, the context remains unchanged. This vulnerability can lead to incorrect assumptions about the error's origin, causing unnecessary kernel panics. The issue arises because the Machine Check Global Status (MCG_STATUS) does not reflect the poison error, leaving the Code Segment (CS) register as the only valid context indicator. Without proper handling, the kernel misinterprets the error as occurring in kernel space, triggering a panic.
Users can upgrade to the latest version of the Linux kernel, where this vulnerability has been addressed. Instructions for downloading the patched kernel are available on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 14, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2e01bdf7203c383e9d8489d9f963c52d6c81e4db | kernel.org | Patch |
| https://git.kernel.org/stable/c/4240e2ebe67941ce2c4f5c866c3af4b5ac7a0c67 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6eac3965901489ae114a664a78cd2d1415d1af5c | kernel.org | Patch |
| https://git.kernel.org/stable/c/e6e6a5f50f58fadec397b23064b7e4830292863d | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | < 6.1.53 >= 6.2, < 6.4.16 >= 6.5, < 6.5.3 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jan 14, 2026 | CVE Modified | CISA-ADP |
| Dec 11, 2025 | Initial Analysis | [email protected] |
| Sep 18, 2025 | New CVE Received | kernel.org |