# CVE-2022-1891: Memory corruption in BIOS

> A local attacker can exploit a buffer overflow in Lenovo Notebook BIOS to execute arbitrary code and escalate privileges.

- **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:** 23 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-f95f-f57p-rc4m

## What is CVE-2022-1891?

CVE-2022-1891 is a medium-severity memory corruption vulnerability in Lenovo BIOS, published on 23 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 SystemLoadDefaultDxe driver in some Lenovo Notebook products may allow an attacker with local privileges to execute arbitrary code.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-122 (Heap-based Buffer Overflow)

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

It affects 6 products.


Products: Lenovo Thinkbook 14-Iil Firmware, Lenovo Thinkbook 14-Iml Firmware, Lenovo Thinkbook 15-Iil Firmware, Lenovo Thinkbook 15-Iml Firmware, Lenovo Yoga C640-13iml Firmware, Lenovo Yoga C640-13iml Lte Firmware.

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

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

## Is CVE-2022-1891 being exploited?

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

## Other vulnerabilities in Lenovo BIOS

- [CVE-2022-1890](https://insights.sbomify.com/CVE-2022-1890/): Memory corruption in BIOS (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1891 is a medium-severity memory corruption vulnerability in Lenovo BIOS, published on 23 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-1891 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-1891/ (Markdown: https://insights.sbomify.com/CVE-2022-1891/index.md)
```

## Sources

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

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