# CVE-2023-41111: Memory corruption in n/a

> Attackers can cause abnormal termination of mobile devices via improper handling of length parameters in the RLC module of Samsung Exynos processors.

- **Severity:** High 7.1 (`CVSS:3.1/AC:L/AV:N/A:H/C:N/I:L/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2023
- **Updated:** 17 Sep 2024
- **Also known as:** A-292004859, GHSA-44j5-cggq-4pgj, PUB-A-292004859

## What is CVE-2023-41111?

CVE-2023-41111 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 8 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Samsung Mobile Processor, Wearable Processor, Automotive Processor, and Modem (Exynos 9810, 9610, 9820, 980, 850, 1080, 2100, 2200, 1280, 1380, 1330, 9110, W920, Modem 5123, Modem 5300, and Auto T5123). Improper handling of a length parameter inconsistency can cause abnormal termination of a mobile phone. This occurs in the RLC task and RLC module.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-41111?

It affects 16 products.


Products: Samsung Exynos 1080 Firmware, Samsung Exynos 1280 Firmware, Samsung Exynos 1330 Firmware, Samsung Exynos 1380 Firmware, Samsung Exynos 2100 Firmware, Samsung Exynos 2200 Firmware, Samsung Exynos 850 Firmware, Samsung Exynos 9110 Firmware, Samsung Exynos 9610 Firmware, Samsung Exynos 980 Firmware, Samsung Exynos 9810 Firmware, Samsung Exynos 9820 Firmware, Samsung Exynos Auto T5123 Firmware, Samsung Exynos Modem 5123 Firmware, Samsung Exynos Modem 5300 Firmware, Samsung Exynos W920 Firmware.

## How do I fix CVE-2023-41111?

Apply the vendor's patch.

## Is CVE-2023-41111 being exploited?

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

## Other vulnerabilities in Samsung Exynos 1080 Firmware

- [CVE-2025-54328](https://insights.sbomify.com/CVE-2025-54328/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-62818](https://insights.sbomify.com/CVE-2025-62818/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-58349](https://insights.sbomify.com/CVE-2025-58349/): Denial of service in n/a (critical 9.1)
- [CVE-2025-27807](https://insights.sbomify.com/CVE-2025-27807/): Memory corruption in n/a (critical 9.1)
- [CVE-2025-47202](https://insights.sbomify.com/CVE-2025-47202/): Memory corruption in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41111 and fix it if it is affected.

What it is: CVE-2023-41111 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 8 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41111 in the wild and no public exploit code.

Affected product: Samsung Exynos 1080 Firmware. 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-2023-41111/ (Markdown: https://insights.sbomify.com/CVE-2023-41111/index.md)
```

## Sources

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

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