# CVE-2026-37540: Integer overflow in n/a

> An integer overflow in the OpenAMP ELF loader allows attackers to cause memory corruption or crashes on 32-bit embedded systems via crafted firmware images.

- **Severity:** High 8.4 (`CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-vc29-cvhx-v56x

## What is CVE-2026-37540?

CVE-2026-37540 is a high-severity vulnerability in n/a, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenAMP v2025.10.0 ELF loader contains an integer overflow vulnerability in firmware image parsing. In elf_loader.c, it performs multiplication of two attacker-controlled 16-bit values from the ELF header without overflow checking. On 32-bit embedded systems (STM32MP1, Zynq, i.MX), large values can cause the product to wrap around to a small value.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-37540?

It affects 1 product.


Products: Linaro Openamp.

## How do I fix CVE-2026-37540?

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

## Is CVE-2026-37540 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37540 and fix it if it is affected.

What it is: CVE-2026-37540 is a high-severity vulnerability in n/a, published on 1 May 2026. 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-2026-37540 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-2026-37540/ (Markdown: https://insights.sbomify.com/CVE-2026-37540/index.md)
```

## Sources

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

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