# CVE-2024-36357: Information disclosure in AMD EPYC™ 7003 Series Processors

> Attackers can infer sensitive data from the L1D cache across privileged boundaries on affected AMD processors, requiring microcode or OS patches.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2024-36357, DEBIAN-CVE-2024-36357, GHSA-76p2-wq47-mf7x, RHBA-2025:15878, ROOT-OS-DEBIAN-11-CVE-2024-36357, ROOT-OS-DEBIAN-12-CVE-2024-36357, ROOT-OS-UBUNTU-2204-CVE-2024-36357, ROOT-OS-UBUNTU-2404-CVE-2024-36357, UBUNTU-CVE-2024-36357

## What is CVE-2024-36357?

CVE-2024-36357 is a medium-severity vulnerability in AMD EPYC™ 7003 Series Processors, published on 8 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.

Weakness: CWE-1421 (Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution)

## Which versions are affected by CVE-2024-36357?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `iwl100-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:39.31.5.1-151.4.el9_6 |
| `iwl1000-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 1:39.31.5.1-151.4.el9_6 |
| `iwl105-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-151.4.el9_6 |
| `iwl135-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-151.4.el9_6 |
| `iwl2000-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-151.4.el9_6 |
| `iwl2030-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-151.4.el9_6 |
| `iwl3160-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 1:25.30.13.0-151.4.el9_6 |
| `iwl5000-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:8.83.5.1_1-151.4.el9_6 |
| `iwl5150-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:8.24.2.2-151.4.el9_6 |
| `iwl6000g2a-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-151.4.el9_6 |
| `iwl6000g2b-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:18.168.6.1-151.4.el9_6 |
| `iwl6050-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:41.28.5.1-151.4.el9_6 |
| `iwl7260-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 1:25.30.13.0-151.4.el9_6 |
| `libertas-sd8787-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:20250812-151.4.el9_6 |
| `linux-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:20250812-151.4.el9_6 |
| `linux-firmware-whence` | Red Hat:enterprise_linux:9::baseos | All versions | 0:20250812-151.4.el9_6 |
| `netronome-firmware` | Red Hat:enterprise_linux:9::baseos | All versions | 0:20250812-151.4.el9_6 |

## How do I fix CVE-2024-36357?

Apply the vendor's patch.

## Is CVE-2024-36357 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36357 and fix it if it is affected.

What it is: CVE-2024-36357 is a medium-severity vulnerability in AMD EPYC™ 7003 Series Processors, published on 8 Jul 2025. 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-2024-36357 in the wild and no public exploit code.

Affected product: AMD EPYC™ 7003 Series 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-2024-36357/ (Markdown: https://insights.sbomify.com/CVE-2024-36357/index.md)
```

## Sources

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

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