Exynos 2200 Firmware: Improper Initialization
CVE-2025-66363 is a high-severity improper initialization vulnerability in Exynos 2200 Firmware from Samsung, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.56% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Exynos 2200 Firmware you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on semiconductor.samsung.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Samsung | Exynos 2200 Firmware | Not specified in the record | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CISA (ADP).
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Initialization
The product does not initialize or incorrectly initializes a resource.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable's type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.
- Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.
- Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Exynos 2200 Firmware
- 9.8 Critical severity
- 7.5 High severity
- 10.0 Critical severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
Recent Improper Initialization vulnerabilities
- 7.5 High severity
- 8.5 High severity
- 9.2 Critical severity
- 7.5 High severity
- 8.8 High severity
- 10.0 Critical severity
Spotted an error? Tell us.