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

> A TOCTOU race condition in the Int15ServiceSmm handler allows DMA attacks to corrupt SMRAM, enabling privilege escalation or code execution.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-mhv9-pjh5-g3cf

## What is CVE-2022-33982?

CVE-2022-33982 is a medium-severity vulnerability in n/a, 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 attacks on the parameter buffer used by the Int15ServiceSmm software SMI handler could lead to a TOCTOU attack on the SMI handler and lead to corruption of SMRAM. DMA attacks on the parameter buffer used by the software SMI handler used by the driver Int15ServiceSmm could lead to a TOCTOU attack on the SMI handler and lead to corruption of SMRAM. This issue was discovered by Insyde engineering during a security review. This issue is fixed in Kernel 5.2: 05.27.23, Kernel 5.3: 05.36.23, Kernel 5.4: 05.44.23 and Kernel 5.5: 05.52.23 CWE-367

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

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

It affects 1 product.


Products: Insyde Kernel.

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

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

## Is CVE-2022-33982 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36337](https://insights.sbomify.com/CVE-2022-36337/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29275](https://insights.sbomify.com/CVE-2022-29275/): Privilege escalation in n/a (high 8.2)
- [CVE-2022-29276](https://insights.sbomify.com/CVE-2022-29276/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29278](https://insights.sbomify.com/CVE-2022-29278/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29279](https://insights.sbomify.com/CVE-2022-29279/): Memory corruption in n/a (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33982 is a medium-severity vulnerability in n/a, 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-33982 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-33982/ (Markdown: https://insights.sbomify.com/CVE-2022-33982/index.md)
```

## Sources

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

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