# CVE-2021-22684: Integer overflow in Tizen RT RTOS

> An integer overflow in Tizen RT RTOS memory allocation functions can cause unexpected behavior and system crashes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 31 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4cwm-fmh5-v7xw

## What is CVE-2021-22684?

CVE-2021-22684 is a high-severity vulnerability in Tizen RT RTOS, published on 31 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tizen RT RTOS version 3.0.GBB is vulnerable to integer wrap-around in functions_calloc and mm_zalloc. This improper memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Samsung Tizenrt.

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

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

## Is CVE-2021-22684 being exploited?

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

## Other vulnerabilities in Tizen RT RTOS

- [CVE-2022-40278](https://insights.sbomify.com/CVE-2022-40278/): Use after free in n/a (high 7.5)
- [CVE-2022-40279](https://insights.sbomify.com/CVE-2022-40279/): Denial of service in n/a (high 7.5)
- [CVE-2022-40280](https://insights.sbomify.com/CVE-2022-40280/): Denial of service in n/a (high 7.5)
- [CVE-2022-40281](https://insights.sbomify.com/CVE-2022-40281/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22684 is a high-severity vulnerability in Tizen RT RTOS, published on 31 Aug 2021. 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-22684 in the wild and no public exploit code.

Affected product: Tizen RT RTOS. 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-22684/ (Markdown: https://insights.sbomify.com/CVE-2021-22684/index.md)
```

## Sources

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

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