# CVE-2025-66363: Other in n/a

> Lack of memory initialization in DL NAS Transport messages in Samsung Exynos 2200 processors may lead to undefined behavior or information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 3 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-m529-qhhc-rjcp

## What is CVE-2025-66363?

CVE-2025-66363 is a high-severity vulnerability in Samsung Exynos 2200 Firmware, published on 3 Mar 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 LBS in Samsung Mobile Processor Exynos 2200. There was no check for memory initialization within DL NAS Transport messages.

Weakness: CWE-665 (Improper Initialization)

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

It affects 1 product.


Products: Samsung Exynos 2200 Firmware.

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

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

## Is CVE-2025-66363 being exploited?

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

## Other vulnerabilities in Samsung Exynos 2200 Firmware

- [CVE-2025-23104](https://insights.sbomify.com/CVE-2025-23104/): Use after free in n/a (medium 6.5)
- [CVE-2024-31957](https://insights.sbomify.com/CVE-2024-31957/): Denial of service in n/a (medium 6.2)
- [CVE-2023-41911](https://insights.sbomify.com/CVE-2023-41911/): Use after free in n/a (medium 4.7)
- [CVE-2023-42482](https://insights.sbomify.com/CVE-2023-42482/): Use after free in n/a (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66363 is a high-severity vulnerability in Samsung Exynos 2200 Firmware, published on 3 Mar 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-66363 in the wild and no public exploit code.

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

## Sources

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

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