# CVE-2022-40250: Stack overflow vulnerability in SMI handler on SmmSmbiosElog.

> Attackers can exploit a stack overflow in SMM to execute arbitrary code, bypass Secure Boot, and install persistent BIOS backdoors.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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:** 20 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-27wf-832r-r7vc

## What is CVE-2022-40250?

CVE-2022-40250 is a high-severity memory corruption vulnerability in AMI Aptio, published on 20 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An attacker can exploit this vulnerability to elevate privileges from ring 0 to ring -2, execute arbitrary code in System Management Mode - an environment more privileged than operating system (OS) and completely isolated from it. Running arbitrary code in SMM additionally bypasses SMM-based SPI flash protections against modifications, which can help an attacker to install a firmware backdoor/implant into BIOS. Such a malicious firmware code in BIOS could persist across operating system re-installs. Additionally, this vulnerability potentially could be used by malicious actors to bypass security mechanisms provided by UEFI firmware (for example, Secure Boot and some types of memory isolation for hypervisors). This issue affects: Module name: SmmSmbiosElog SHA256: 3a8acb4f9bddccb19ec3b22b22ad97963711550f76b27b606461cd5073a93b59 Module GUID: 8e61fd6b-7a8b-404f-b83f-aa90a47cabdf This issue affects: AMI Aptio 5.x. This issue affects: AMI Aptio 5.x.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 3 products.


Products: Ami Aptio V, Intel Nuc M15 Laptop Kit Lapbc510 Firmware, Intel Nuc M15 Laptop Kit Lapbc710 Firmware.

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

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

## Is CVE-2022-40250 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40250 exists.

## Other vulnerabilities in AMI Aptio

- [CVE-2025-33045](https://insights.sbomify.com/CVE-2025-33045/): Legacy Serial Redirection SMRAM Vulnerabilities (high 8.2)
- [CVE-2022-26873](https://insights.sbomify.com/CVE-2022-26873/): Memory corruption in Aptio (high 8.2)
- [CVE-2022-40261](https://insights.sbomify.com/CVE-2022-40261/): SMM memory corruption vulnerability in OverClockSmiHandler SMM driver (high 8.2)
- [CVE-2022-40262](https://insights.sbomify.com/CVE-2022-40262/): The arbitrary write vulnerability in S3Resume2Pei leads to arbitrary code execution during PEI phase. (high 8.2)
- [CVE-2024-33656](https://insights.sbomify.com/CVE-2024-33656/): Memory Leak in SmmComuptrace Module (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40250 is a high-severity memory corruption vulnerability in AMI Aptio, published on 20 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40250 exists.

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

## Sources

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

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