An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200,
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, W920, W930, W1000, Modem 5123, and Modem 5300. The UE incorrectly handles a malformed uplink scheduling message, resulting in an information leak of the UE.
- Published
- Jan 13, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-922
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| samsung | exynos modem 5123 firmware | cpe:2.3:o:samsung:exynos_modem_5123_firmware |
| samsung | exynos modem 5123 | cpe:2.3:h:samsung:exynos_modem_5123 |
| samsung | exynos modem 5300 firmware | cpe:2.3:o:samsung:exynos_modem_5300_firmware |
| samsung | exynos modem 5300 | cpe:2.3:h:samsung:exynos_modem_5300 |
| samsung | exynos 9820 firmware | cpe:2.3:o:samsung:exynos_9820_firmware |
| samsung | exynos 9820 | cpe:2.3:h:samsung:exynos_9820 |
| samsung | exynos 9825 firmware | cpe:2.3:o:samsung:exynos_9825_firmware |
| samsung | exynos 9825 | cpe:2.3:h:samsung:exynos_9825 |
| samsung | exynos 980 firmware | cpe:2.3:o:samsung:exynos_980_firmware |
| samsung | exynos 980 | cpe:2.3:h:samsung:exynos_980 |
| samsung | exynos 990 firmware | cpe:2.3:o:samsung:exynos_990_firmware |
| samsung | exynos 990 | cpe:2.3:h:samsung:exynos_990 |
and 26 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- samsung exynos 1080 firmwareall versions
- samsung exynos 1280 firmwareall versions
- samsung exynos 1330 firmwareall versions
- samsung exynos 1380 firmwareall versions
- samsung exynos 1480 firmwareall versions
- samsung exynos 2100 firmwareall versions
- samsung exynos 2200 firmwareall versions
- samsung exynos 2400 firmwareall versions
- samsung exynos 850 firmwareall versions
- samsung exynos 9110 firmwareall versions
- samsung exynos 980 firmwareall versions
- samsung exynos 9820 firmwareall versions
- samsung exynos 9825 firmwareall versions
- samsung exynos 990 firmwareall versions
- samsung exynos modem 5123 firmwareall versions
- samsung exynos modem 5300 firmwareall versions
- samsung exynos w1000 firmwareall versions
- samsung exynos w920 firmwareall versions
- samsung exynos w930 firmwareall versions
Same product
samsung: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-50806A vulnerability was discovered in Samsung Mobile Processor, Wearable Processor, and Modems with versions Exynos 9820, Exynos 9825, Exynos 9833Monitor
- CVE-2024-39890An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200,32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-922 · Insecure Storage of Sensitive InformationCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.