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

> A use-after-free vulnerability in the m2m scaler driver of Samsung Exynos processors allows attackers to escalate privileges.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 7 Oct 2024
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-frrh-j3wr-gprp

## What is CVE-2024-44068?

CVE-2024-44068 is a high-severity use after free vulnerability in Samsung Exynos 850 Firmware, published on 7 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the m2m scaler driver in Samsung Mobile Processor and Wearable Processor Exynos 9820, 9825, 980, 990, 850,and W920. A Use-After-Free in the mobile processor leads to privilege escalation.

Weakness: CWE-416 (Use After Free)

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

It affects 6 products.


Products: Samsung Exynos 850 Firmware, Samsung Exynos 980 Firmware, Samsung Exynos 9820 Firmware, Samsung Exynos 9825 Firmware, Samsung Exynos 990 Firmware, Samsung Exynos W920 Firmware.

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

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

## Is CVE-2024-44068 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44068 is a high-severity use after free vulnerability in Samsung Exynos 850 Firmware, published on 7 Oct 2024. 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-2024-44068 in the wild and no public exploit code.

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

## Sources

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

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