# CVE-2025-54602: Use after free in n/a

> A race condition in the Samsung Exynos Wi-Fi driver allows attackers to trigger a use-after-free via concurrent ioctl calls, potentially enabling code execution or privilege escalation.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-c585-9w92-v4hm

## What is CVE-2025-54602?

CVE-2025-54602 is a high-severity use after free vulnerability in Samsung Exynos 1080 Firmware, published on 6 Apr 2026. 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 the Wi-Fi driver in Samsung Mobile Processor and Wearable Processor Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, and W1000. Improper synchronization on a global variable leads to a use-after-free. An attacker can trigger a race condition by invoking an ioctl function concurrently from multiple threads.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2025-54602?

It affects 11 products.


Products: Samsung Exynos 1080 Firmware, Samsung Exynos 1280 Firmware, Samsung Exynos 1330 Firmware, Samsung Exynos 1380 Firmware, Samsung Exynos 1480 Firmware, Samsung Exynos 1580 Firmware, Samsung Exynos 850 Firmware, Samsung Exynos 980 Firmware, Samsung Exynos W1000 Firmware, Samsung Exynos W920 Firmware, Samsung Exynos W930 Firmware.

## How do I fix CVE-2025-54602?

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

## Is CVE-2025-54602 being exploited?

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

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

## Sources

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

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