# CVE-2023-31356: Memory corruption in AMD EPYC™ 7003 Processors

> A privileged attacker can corrupt guest private memory due to incomplete cleanup in AMD SEV firmware, compromising data integrity.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2024
- **Updated:** 11 Feb 2025
- **Also known as:** DEBIAN-CVE-2023-31356, GHSA-3w7r-v4fr-r43w, RHSA-2024:7482, UBUNTU-CVE-2023-31356

## What is CVE-2023-31356?

CVE-2023-31356 is a medium-severity memory corruption vulnerability in AMD EPYC™ 7003 Processors, published on 13 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incomplete system memory cleanup in SEV firmware could
allow a privileged attacker to corrupt guest private memory, potentially
resulting in a loss of data integrity.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2023-31356?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `iwl100-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:39.31.5.1-118.3.el8_8.1 |
| `iwl1000-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 1:39.31.5.1-118.3.el8_8.1 |
| `iwl105-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:18.168.6.1-118.3.el8_8.1 |
| `iwl135-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:18.168.6.1-118.3.el8_8.1 |
| `iwl2000-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:18.168.6.1-118.3.el8_8.1 |
| `iwl2030-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:18.168.6.1-118.3.el8_8.1 |
| `iwl3160-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 1:25.30.13.0-118.3.el8_8.1 |
| `iwl3945-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:15.32.2.9-118.3.el8_8.1 |
| `iwl4965-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:228.61.2.24-118.3.el8_8.1 |
| `iwl5000-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:8.83.5.1_1-118.3.el8_8.1 |
| `iwl5150-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:8.24.2.2-118.3.el8_8.1 |
| `iwl6000-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:9.221.4.1-118.3.el8_8.1 |
| `iwl6000g2a-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:18.168.6.1-118.3.el8_8.1 |
| `iwl6000g2b-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:18.168.6.1-118.3.el8_8.1 |
| `iwl6050-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:41.28.5.1-118.3.el8_8.1 |
| `iwl7260-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 1:25.30.13.0-118.3.el8_8.1 |
| `libertas-sd8686-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:20240827-118.3.git3cff7109.el8_8 |
| `libertas-sd8787-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:20240827-118.3.git3cff7109.el8_8 |
| `libertas-usb8388-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 2:20240827-118.3.git3cff7109.el8_8 |
| `libertas-usb8388-olpc-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:20240827-118.3.git3cff7109.el8_8 |
| `linux-firmware` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:20240827-118.3.git3cff7109.el8_8 |

## How do I fix CVE-2023-31356?

Apply the vendor's patch.

## Is CVE-2023-31356 being exploited?

There is no known exploitation of CVE-2023-31356 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31356 and fix it if it is affected.

What it is: CVE-2023-31356 is a medium-severity memory corruption vulnerability in AMD EPYC™ 7003 Processors, published on 13 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31356 in the wild and no public exploit code.

Affected product: AMD EPYC™ 7003 Processors. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-31356/ (Markdown: https://insights.sbomify.com/CVE-2023-31356/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-31356
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-31356
- OSV: https://osv.dev/vulnerability/CVE-2023-31356

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-31356/
Summaries are generated and may contain mistakes; the official description above is the record.