# CVE-2021-22680: NXP MQX Integer Overflow or Wraparound

> An integer overflow in NXP MQX memory allocation functions allows attackers to cause crashes or execute arbitrary code.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-vg7p-p52h-xg3x

## What is CVE-2021-22680?

CVE-2021-22680 is a high-severity vulnerability in NXP MQX, published on 3 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NXP MQX Versions 5.1 and prior are vulnerable to integer overflow in mem_alloc, _lwmem_alloc and _partition functions. This unverified memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash or a remote code injection/execution.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2021-22680?

It affects 1 product.


Products: Nxp Mqx.

## How do I fix CVE-2021-22680?

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

## Is CVE-2021-22680 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22680 and fix it if it is affected.

What it is: CVE-2021-22680 is a high-severity vulnerability in NXP MQX, published on 3 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22680 in the wild and no public exploit code.

Affected product: NXP MQX. 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-2021-22680/ (Markdown: https://insights.sbomify.com/CVE-2021-22680/index.md)
```

## Sources

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

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