# CVE-2022-40137: Memory corruption in BIOS

> Local attackers with elevated privileges can execute arbitrary code via a buffer overflow in the Lenovo BIOS WMI SMI Handler.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/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:** 30 Jan 2023
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-wqx8-q4r7-4c45

## What is CVE-2022-40137?

CVE-2022-40137 is a medium-severity memory corruption vulnerability in Lenovo BIOS, published on 30 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A buffer overflow in the WMI SMI Handler in some Lenovo models may allow an attacker with local access and elevated privileges to execute arbitrary code.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 287 products.


Products: Lenovo Ideacentre 3-07ada05 Firmware, Lenovo Ideacentre 3-07imb05 Firmware, Lenovo Ideacentre 3 07iab7 Firmware, Lenovo Ideacentre 5-14acn6 Firmware, Lenovo Ideacentre 5-14are05 Firmware, Lenovo Ideacentre 5-14imb05 Firmware, Lenovo Ideacentre 5-14iob6 Firmware, Lenovo Ideacentre 510-15ick Firmware, Lenovo Ideacentre 510a-15arr Firmware, Lenovo Ideacentre 510a-15ick Firmware, Lenovo Ideacentre 510s-07icb Firmware, Lenovo Ideacentre 510s-07ick Firmware, Lenovo Ideacentre 5 14iab7 Firmware, Lenovo Ideacentre 720-18apr Firmware, Lenovo Ideacentre A340-22ast All-in-One Firmware, Lenovo Ideacentre A340-22icb All-in-One Firmware, Lenovo Ideacentre A340-22ick All-in-One Firmware, Lenovo Ideacentre A340-22igm All-in-One Firmware, Lenovo Ideacentre A340-22iwl All-in-One Firmware, Lenovo Ideacentre A340-24icb All-in-One Firmware and 267 more.

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

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

## Is CVE-2022-40137 being exploited?

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

## Other vulnerabilities in Lenovo BIOS

- [CVE-2023-43567](https://insights.sbomify.com/CVE-2023-43567/): Memory corruption in Desktop BIOS (medium 6.7)
- [CVE-2023-43569](https://insights.sbomify.com/CVE-2023-43569/): Memory corruption in Desktop BIOS (medium 6.7)
- [CVE-2023-43570](https://insights.sbomify.com/CVE-2023-43570/): Code injection in Desktop BIOS (medium 6.7)
- [CVE-2023-43571](https://insights.sbomify.com/CVE-2023-43571/): Memory corruption in Desktop BIOS (medium 6.7)
- [CVE-2023-43573](https://insights.sbomify.com/CVE-2023-43573/): Memory corruption in Desktop BIOS (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40137 is a medium-severity memory corruption vulnerability in Lenovo BIOS, published on 30 Jan 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-40137 in the wild and no public exploit code.

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

## Sources

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

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