Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-37540 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Linaro Openamp. Its CVSS base score is 8.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-37540 is an integer overflow vulnerability (CWE-190) in the ELF loader of OpenAMP version 2025.10.0. The issue resides in elf_loader.c, where the code multiplies two attacker-controlled 16-bit values from the ELF header without overflow checking. On 32-bit embedded systems such as STM32MP1, Zynq, and i.MX, large input values cause the product to wrap around to a small value, published on 2026-05-01 with a CVSS v3.1 score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
A local attacker with no privileges can exploit this vulnerability with low attack complexity and no user interaction. By providing a malicious ELF firmware image, the attacker triggers the overflow during parsing, potentially leading to high impacts on confidentiality, integrity, and availability.
Mitigation details are available in related advisories and source code references, including the primary disclosure at https://gist.github.com/sgInnora/f4ac66faeefe07a653ceeb3f58cdc381, the OpenAMP repository at https://github.com/OpenAMP/open-amp, and the affected elf_loader.c file at https://github.com/OpenAMP/open-amp/blob/main/lib/remoteproc/elf_loader.c.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26693
Vulnerability Data
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…
more
cause the product to wrap around to a small value.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.