# CVE-2022-29900: Other in AMD Processors

> Mis-trained branch predictions in AMD processors allow arbitrary speculative code execution, potentially exposing sensitive data or enabling code injection.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/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:** 12 Jul 2022
- **Updated:** 20 Nov 2024
- **Also known as:** ALPINE-CVE-2022-29900, DEBIAN-CVE-2022-29900, GHSA-f3p5-98fc-2gxr, UBUNTU-CVE-2022-29900

## What is CVE-2022-29900?

CVE-2022-29900 is a medium-severity vulnerability in Amd Epyc 7252 Firmware, published on 12 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Mis-trained branch predictions for return instructions may allow arbitrary speculative code execution under certain microarchitecture-dependent conditions.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2022-29900?

It affects 126 products.


Products: Amd A10-9600p Firmware, Amd A10-9630p Firmware, Amd A12-9700p Firmware, Amd A12-9730p Firmware, Amd A4-9120 Firmware, Amd A6-9210 Firmware, Amd A6-9220 Firmware, Amd A6-9220c Firmware, Amd A9-9410 Firmware, Amd A9-9420 Firmware, Amd Athlon Gold 3150u Firmware, Amd Athlon Silver 3050u Firmware, Amd Athlon X4 750 Firmware, Amd Athlon X4 760k Firmware, Amd Athlon X4 830 Firmware, Amd Athlon X4 835 Firmware, Amd Athlon X4 840 Firmware, Amd Athlon X4 845 Firmware, Amd Athlon X4 860k Firmware, Amd Athlon X4 870k Firmware and 106 more.

## How do I fix CVE-2022-29900?

Apply the vendor's patch.

## Is CVE-2022-29900 being exploited?

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

Public exploit code:

- Reproduction of the Retbleed (CVE-2022-29900/29901) micro-architectural attack in gem5. RSB underflow, Flush+Reload side-channel leak, and a verified lfence mitigation. (github_poc): https://github.com/abdul-kalam2000/retbleed-speculative-execution-poc

## Other vulnerabilities in Amd Epyc 7252 Firmware

- [CVE-2022-23825](https://insights.sbomify.com/CVE-2022-23825/): Information disclosure in AMD Processors (medium 6.5)
- [CVE-2022-23823](https://insights.sbomify.com/CVE-2022-23823/): Information disclosure in AMD Processors (medium 6.5)
- [CVE-2021-26341](https://insights.sbomify.com/CVE-2021-26341/): Information disclosure in AMD Processors (medium 6.5)
- [CVE-2021-26401](https://insights.sbomify.com/CVE-2021-26401/): Security feature bypass in AMD Processors (medium 5.6)
- [CVE-2022-23824](https://insights.sbomify.com/CVE-2022-23824/): Information disclosure in AMD Processors (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29900 and fix it if it is affected.

What it is: CVE-2022-29900 is a medium-severity vulnerability in Amd Epyc 7252 Firmware, published on 12 Jul 2022. 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-2022-29900 in the wild and no public exploit code.

Affected product: Amd Epyc 7252 Firmware. 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-2022-29900/ (Markdown: https://insights.sbomify.com/CVE-2022-29900/index.md)
```

## Sources

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

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