# CVE-2024-32503: Use after free in n/a

> A use-after-free vulnerability in Samsung Exynos processors allows attackers to potentially execute arbitrary code or escalate privileges.

- **Severity:** High 8.4 (`CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-273h-mfpf-cvq6

## What is CVE-2024-32503?

CVE-2024-32503 is a high-severity use after free vulnerability in Samsung Exynos 1080 Firmware, published on 7 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 and Wearable Processor Exynos 850, Exynos 1080, Exynos 2100, Exynos 1280, Exynos 1380, Exynos 1330, Exynos W920, Exynos W930. The mobile processor lacks proper memory deallocation checking, which can result in a UAF (Use-After-Free) vulnerability.

Weakness: CWE-416 (Use After Free), CWE-762 (Mismatched Memory Management Routines)

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

It affects 8 products.


Products: Samsung Exynos 1080 Firmware, Samsung Exynos 1280 Firmware, Samsung Exynos 1330 Firmware, Samsung Exynos 1380 Firmware, Samsung Exynos 2100 Firmware, Samsung Exynos 850 Firmware, Samsung Exynos W920 Firmware, Samsung Exynos W930 Firmware.

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

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

## Is CVE-2024-32503 being exploited?

There is no known exploitation of CVE-2024-32503 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-2024-32503 and fix it if it is affected.

What it is: CVE-2024-32503 is a high-severity use after free vulnerability in Samsung Exynos 1080 Firmware, published on 7 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-32503 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-2024-32503/ (Markdown: https://insights.sbomify.com/CVE-2024-32503/index.md)
```

## Sources

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

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