# CVE-2024-36315: Information disclosure in AMD EPYC™ 8004 Series Processors

> Attackers can bypass speculation barriers to disclose sensitive information on affected AMD processors, requiring firmware updates.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-48h8-ccw7-958p, UBUNTU-CVE-2024-36315

## What is CVE-2024-36315?

CVE-2024-36315 is a medium-severity vulnerability in AMD EPYC™ 8004 Series Processors, published on 13 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper enforcement of the LFENCE serialization property may allow an attacker to bypass speculation barriers and potentially disclose sensitive information, potentially resulting in loss of confidentiality.

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

Apply the vendor's patch.

## Is CVE-2024-36315 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36315 is a medium-severity vulnerability in AMD EPYC™ 8004 Series Processors, published on 13 May 2026. 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-36315 in the wild and no public exploit code.

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

## Sources

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

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