Skip to main content
CVE-2025-23102VulnerabilityPublished Updated

CVE-2025-23102: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

Given the absence of publicly available patches, European organizations should implement a multi-layered mitigation strategy. First, they should inventory and identify all devices using the affected Exynos processors to assess exposure. Network-level protections such as strict firewall rules, intrusion detection/prevention systems (IDS/IPS), and anomaly detection should be enhanced to monitor for suspicious activity indicative of exploitation attempts. Organizations should enforce the principle of least privilege on mobile devices, restricting app permissions and disabling unnecessary services to reduce attack surface. Mobile Device Management (MDM) solutions should be used to enforce security policies, deploy updates promptly once patches become available, and remotely isolate or wipe compromised devices. Users should be educated about the risks and advised to avoid connecting to untrusted networks. Collaboration with device vendors and carriers is critical to accelerate patch development and deployment. Until patches are released, organizations might consider restricting the use of vulnerable devices for sensitive operations or deploying additional endpoint security controls that can detect exploitation behaviors. Regular security audits and penetration testing focusing on mobile device security can help identify potential exploitation paths.

Description

An issue was discovered in Samsung Mobile Processor Exynos 980, 990, 1080, 2100, 1280, 2200, 1380, 1480 and 2400. A Double Free in the mobile processor leads to privilege escalation.

References

Community reviews

Loading reviews…