# CVE-2025-52908: Memory corruption in n/a

> A buffer overflow in the Exynos Wi-Fi driver allows attackers to execute arbitrary code or escalate privileges via crafted ioctl messages.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-326f-rc6r-57wf

## What is CVE-2025-52908?

CVE-2025-52908 is a critical memory corruption vulnerability in Samsung Exynos 1280 Firmware, published on 7 Apr 2026. 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 Wi-Fi driver in Samsung Mobile Processor and Wearable Processor Exynos 980, 850, 1280, 1330, 1380, 1480, 1580, W920, W930, and W1000. Incorrect Handling of the NL80211 vendor command leads to a buffer overflow via a certain ioctl message, issue 1 of 2.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 10 products.


Products: 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-52908?

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

## Is CVE-2025-52908 being exploited?

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

## Other vulnerabilities in Samsung Exynos 1280 Firmware

- [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)
- [CVE-2025-62817](https://insights.sbomify.com/CVE-2025-62817/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52908 and fix it if it is affected.

What it is: CVE-2025-52908 is a critical memory corruption vulnerability in Samsung Exynos 1280 Firmware, published on 7 Apr 2026. 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-2025-52908 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-2025-52908/ (Markdown: https://insights.sbomify.com/CVE-2025-52908/index.md)
```

## Sources

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

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