# CVE-2022-29275: Privilege escalation in n/a

> Untrusted input in UsbCoreDxe allows OS or SMRAM memory tampering, leading to privilege escalation in Insyde BIOS firmware.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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:** 15 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-ph2x-fwr9-vjxc

## What is CVE-2022-29275?

CVE-2022-29275 is a high-severity 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

In UsbCoreDxe, untrusted input may allow SMRAM or OS memory tampering Use of untrusted pointers could allow OS or SMRAM memory tampering leading to escalation of privileges. This issue was discovered by Insyde during security review. It was fixed in: Kernel 5.0: version 05.09.21 Kernel 5.1: version 05.17.21 Kernel 5.2: version 05.27.21 Kernel 5.3: version 05.36.21 Kernel 5.4: version 05.44.21 Kernel 5.5: version 05.52.21 https://www.insyde.com/security-pledge/SA-2022058

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Insyde Kernel.

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

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

## Is CVE-2022-29275 being exploited?

There is no known exploitation of CVE-2022-29275 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-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)
- [CVE-2022-30771](https://insights.sbomify.com/CVE-2022-30771/): Memory corruption in n/a (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29275 is a high-severity 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-29275 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-29275/ (Markdown: https://insights.sbomify.com/CVE-2022-29275/index.md)
```

## Sources

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

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