# CVE-2021-26706: Integer overflow in n/a

> Integer overflow in memory pool allocation functions allows attackers to create undersized pools, potentially leading to code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7j9p-4w63-5mq8

## What is CVE-2021-26706?

CVE-2021-26706 is a critical vulnerability in n/a, published on 24 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in lib_mem.c in Micrium uC/OS uC/LIB 1.38.x and 1.39.00. The following memory allocation functions do not check for integer overflow when allocating a pool whose size exceeds the address space: Mem_PoolCreate, Mem_DynPoolCreate, and Mem_DynPoolCreateHW. Because these functions use multiplication to calculate the pool sizes, the operation may cause an integer overflow if the arguments are large enough. The resulting memory pool will be smaller than expected and may be exploited by an attacker.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Micrium Uc\/Lib.

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

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

## Is CVE-2021-26706 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-26706 is a critical vulnerability in n/a, published on 24 Jan 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-26706 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-2021-26706/ (Markdown: https://insights.sbomify.com/CVE-2021-26706/index.md)
```

## Sources

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

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