# CVE-2021-27411: Micrium OS Integer Overflow or Wraparound

> Integer overflow in Micrium OS memory pool creation functions can cause unexpected memory allocation behavior, potentially leading to system instability or denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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-823g-7fp8-5vqm

## What is CVE-2021-27411?

CVE-2021-27411 is a medium-severity vulnerability in Micrium OS, published on 3 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Micrium OS Versions 5.10.1 and prior are vulnerable to integer wrap-around in functions Mem_DynPoolCreate, Mem_DynPoolCreateHW and Mem_PoolCreate. This unverified memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as very small blocks of memory being allocated instead of very large ones.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Silabs Micrium Os.

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

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

## Is CVE-2021-27411 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-27411 is a medium-severity vulnerability in Micrium OS, 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-27411 in the wild and no public exploit code.

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

## Sources

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

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