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

> Attackers can exploit a TOCTOU race condition in InsydeH2O BIOS to corrupt SMRAM and escalate privileges via DMA attacks.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/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 Feb 2023
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-7pmf-jrh8-vg99

## What is CVE-2022-32954?

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

### Official description

An issue was discovered in Insyde InsydeH2O with kernel 5.1 through 5.5. DMA attacks on the SdMmcDevice buffer used by SMM and non-SMM code could cause TOCTOU race-condition issues that could lead to corruption of SMRAM and escalation of privileges. This attack can be mitigated by using IOMMU protection for the ACPI runtime memory used for the command buffer. This attack can be mitigated by copying the link data to SMRAM before checking it and verifying that all pointers are within the buffer.

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

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

It affects 1 product.


Products: Insyde Insydeh2o.

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

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

## Is CVE-2022-32954 being exploited?

There is no known exploitation of CVE-2022-32954 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-32954 and fix it if it is affected.

What it is: CVE-2022-32954 is a high-severity vulnerability in Insyde Insydeh2o, published on 15 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-32954 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-32954/ (Markdown: https://insights.sbomify.com/CVE-2022-32954/index.md)
```

## Sources

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

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