# CVE-2022-29277: Memory corruption in n/a

> Incorrect pointer checks in the FwBlockServiceSmm driver allow arbitrary RAM modifications, potentially leading to code execution or privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** No
- **Published:** 15 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-88wh-qc3q-cp9g

## What is CVE-2022-29277?

CVE-2022-29277 is a high-severity memory corruption vulnerability in n/a, published on 15 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect pointer checks within the the FwBlockServiceSmm driver can allow arbitrary RAM modifications During review of the FwBlockServiceSmm driver, certain instances of SpiAccessLib could be tricked into writing 0xff to arbitrary system and SMRAM addresses. Fixed in: INTEL Purley-R: 05.21.51.0048 Whitley: 05.42.23.0066 Cedar Island: 05.42.11.0021 Eagle Stream: 05.44.25.0052 Greenlow/Greenlow-R(skylake/kabylake): Trunk Mehlow/Mehlow-R (CoffeeLake-S): Trunk Tatlow (RKL-S): Trunk Denverton: 05.10.12.0042 Snow Ridge: Trunk Graneville DE: 05.05.15.0038 Grangeville DE NS: 05.27.26.0023 Bakerville: 05.21.51.0026 Idaville: 05.44.27.0030 Whiskey Lake: Trunk Comet Lake-S: Trunk Tiger Lake H/UP3: 05.43.12.0052 Alder Lake: 05.44.23.0047 Gemini Lake: Not Affected Apollo Lake: Not Affected Elkhart Lake: 05.44.30.0018 AMD ROME: trunk MILAN: 05.36.10.0017 GENOA: 05.52.25.0006 Snowy Owl: Trunk R1000: 05.32.50.0018 R2000: 05.44.30.0005 V2000: Trunk V3000: 05.44.30.0007 Ryzen 5000: 05.44.30.0004 Embedded ROME: Trunk Embedded MILAN: Trunk Hygon Hygon #1/#2: 05.36.26.0016 Hygon #3: 05.44.26.0007 https://www.insyde.com/security-pledge/SA-2022060

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 39 products.


Products: Amd Genoa Firmware, Amd Hygon 1 Firmware, Amd Hygon 2 Firmware, Amd Hygon 3 Firmware, Amd Milan Firmware, Amd Rome Firmware, Amd Ryzen 5300g Firmware, Amd Ryzen 5300ge Firmware, Amd Ryzen 5600g Firmware, Amd Ryzen 5600ge Firmware, Amd Ryzen 5600x Firmware, Amd Ryzen 5700g Firmware, Amd Ryzen 5700ge Firmware, Amd Ryzen 5800x3d Firmware, Amd Ryzen 5800x Firmware, Amd Ryzen 5900x Firmware, Amd Ryzen 5950x Firmware, Amd Snowy Owl R1000 Firmware, Amd Snowy Owl R2000 Firmware, Amd Snowy Owl V2000 Firmware and 19 more.

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

No fix has been published for CVE-2022-29277 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-29277 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29277 is a high-severity memory corruption vulnerability in n/a, published on 15 Nov 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-29277 in the wild and no public exploit code.

Affected product: n/a. 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-29277/ (Markdown: https://insights.sbomify.com/CVE-2022-29277/index.md)
```

## Sources

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

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