# CVE-2022-27672: Information disclosure in 1st Gen AMD EPYC™ Processors

> AMD processors may leak sensitive information via speculative execution across sibling threads when SMT is enabled.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/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:** 14 Feb 2023
- **Updated:** 13 Apr 2026
- **Also known as:** ALPINE-CVE-2022-27672, DEBIAN-CVE-2022-27672, GHSA-vxpc-466w-pjjv, ROOT-OS-DEBIAN-11-CVE-2022-27672, SUSE-SU-2023:0692-1, UBUNTU-CVE-2022-27672, openSUSE-SU-2024:12715-1

## What is CVE-2022-27672?

CVE-2022-27672 is a medium-severity vulnerability in Amd Epyc 7232p Firmware, published on 14 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When SMT is enabled, certain AMD processors may speculatively execute instructions using a target
from the sibling thread after an SMT mode switch potentially resulting in information disclosure.

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

It affects 165 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xen` | SUSE:Linux Enterprise Micro 5.3 | All versions | 4.16.3_04-150400.4.22.1 |
| `xen` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 4.16.3_04-150400.4.22.1 |
| `xen` | SUSE:Linux Enterprise Module for Server Applications 15 SP4 | All versions | 4.16.3_04-150400.4.22.1 |
| `xen` | openSUSE:Leap 15.4 | All versions | 4.16.3_04-150400.4.22.1 |
| `xen` | openSUSE:Leap Micro 5.3 | All versions | 4.16.3_04-150400.4.22.1 |
| `xen` | openSUSE:Tumbleweed | All versions | 4.17.0_04-3.1 |

Products: Amd A10-9600p Firmware, Amd A10-9630p Firmware, Amd A12-9700p Firmware, Amd A12-9730p Firmware, Amd A4-9120 Firmware, Amd A4-9120c Firmware, Amd A6-9210 Firmware, Amd A6-9220 Firmware, Amd A6-9220c Firmware, Amd A9-9410 Firmware, Amd A9-9420 Firmware, Amd Athlon Gold 3150c Firmware, Amd Athlon Gold 3150u Firmware, Amd Athlon Gold 7220u Firmware, Amd Athlon Pro 300u Firmware, Amd Athlon Pro 3045b Firmware, Amd Athlon Pro 3145b Firmware, Amd Athlon Silver 3050c Firmware, Amd Athlon Silver 3050e Firmware, Amd Athlon Silver 3050u Firmware and 145 more.

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

Apply the vendor's patch.

## Is CVE-2022-27672 being exploited?

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

## Other vulnerabilities in Amd Epyc 7232p Firmware

- [CVE-2022-23825](https://insights.sbomify.com/CVE-2022-23825/): Information disclosure in AMD Processors (medium 6.5)
- [CVE-2022-29900](https://insights.sbomify.com/CVE-2022-29900/): Other 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27672 is a medium-severity vulnerability in Amd Epyc 7232p Firmware, published on 14 Feb 2023. 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-27672 in the wild and no public exploit code.

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

## Sources

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

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