# CVE-2024-27371: Memory corruption in n/a

> Missing input validation in Exynos processor firmware allows heap overwrite, potentially enabling code execution or privilege escalation.

- **Severity:** Medium 6.7 (`CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:H/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-5vhq-c669-fmgr

## What is CVE-2024-27371?

CVE-2024-27371 is a medium-severity memory corruption vulnerability in Samsung Exynos 1280 Firmware, published on 5 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. In the function slsi_nan_followup_get_nl_params(), there is no input validation check on hal_req->service_specific_info_len coming from userspace, which can lead to a heap overwrite.

Weakness: CWE-787 (Out-of-bounds Write), CWE-1288 (Improper Validation of Consistency within Input)

## Which versions are affected by CVE-2024-27371?

It affects 5 products.


Products: Samsung Exynos 1280 Firmware, Samsung Exynos 1330 Firmware, Samsung Exynos 1380 Firmware, Samsung Exynos 850 Firmware, Samsung Exynos 980 Firmware.

## How do I fix CVE-2024-27371?

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

## Is CVE-2024-27371 being exploited?

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

## Other vulnerabilities in Samsung Exynos 1280 Firmware

- [CVE-2025-52908](https://insights.sbomify.com/CVE-2025-52908/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-52909](https://insights.sbomify.com/CVE-2025-52909/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-52910](https://insights.sbomify.com/CVE-2025-52910/): Use after free in n/a (critical 9.8)
- [CVE-2023-26076](https://insights.sbomify.com/CVE-2023-26076/): Memory corruption in n/a (high 7.6)
- [CVE-2025-62814](https://insights.sbomify.com/CVE-2025-62814/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27371 and fix it if it is affected.

What it is: CVE-2024-27371 is a medium-severity memory corruption vulnerability in Samsung Exynos 1280 Firmware, published on 5 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-27371 in the wild and no public exploit code.

Affected product: Samsung Exynos 1280 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-2024-27371/ (Markdown: https://insights.sbomify.com/CVE-2024-27371/index.md)
```

## Sources

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

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