# CVE-2022-34325: Race condition in n/a

> Attackers can corrupt SMRAM via TOCTOU race conditions in StorageSecurityCommandDxe, enabling privilege escalation or code execution in Insyde BIOS.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/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:** 14 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-gqmx-7hj9-m7jj

## What is CVE-2022-34325?

CVE-2022-34325 is a high-severity vulnerability in Insyde Insydeh2o, published on 14 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DMA transactions which are targeted at input buffers used for the StorageSecurityCommandDxe software SMI handler could cause SMRAM corruption through a TOCTOU attack. DMA transactions which are targeted at input buffers used for the software SMI handler used by the StorageSecurityCommandDxe driver could cause SMRAM corruption. This issue was discovered by Insyde engineering based on the general description provided by

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 1 product.


Products: Insyde Insydeh2o.

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

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

## Is CVE-2022-34325 being exploited?

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

## Other vulnerabilities in Insyde Insydeh2o

- [CVE-2021-41842](https://insights.sbomify.com/CVE-2021-41842/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-22612](https://insights.sbomify.com/CVE-2023-22612/): Memory corruption in n/a (high 8.8)
- [CVE-2023-22613](https://insights.sbomify.com/CVE-2023-22613/): Memory corruption in n/a (high 8.8)
- [CVE-2023-22614](https://insights.sbomify.com/CVE-2023-22614/): Memory corruption in n/a (high 8.8)
- [CVE-2023-22615](https://insights.sbomify.com/CVE-2023-22615/): Memory corruption in n/a (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34325 is a high-severity vulnerability in Insyde Insydeh2o, published on 14 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-34325 in the wild and no public exploit code.

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

## Sources

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

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