Skip to main content
CVE-2025-21008VulnerabilityPublished

CVE-2025-21008: Samsung Mobile libsavsvc.so · Out-of-bounds Read

Affects Samsung Mobile libsavsvc.soSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium : upgrade to 15 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 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

Upgrade Samsung Mobile libsavsvc.so to 15.

Affected software

ProductAffectedFixed in
Samsung Mobile libsavsvc.soAffected
  • <15
Fixed in
  • 15

AI-suggested

If you cannot patch yet, organizations should enforce strict device usage policies limiting physical access to devices and monitor for unusual device behavior indicative of memory corruption or crashes. Employing mobile threat defense (MTD) solutions that detect anomalous app behavior or memory issues can help identify exploitation attempts. Restrict installation of untrusted or unnecessary applications to reduce the risk of local compromise. For devices used in sensitive environments, consider disabling or restricting access to vulnerable multimedia processing features if feasible. Additionally, organizations should educate users on the risks of local device compromise and enforce strong authentication and encryption to prevent unauthorized physical access. Regularly auditing device firmware and software versions across the mobile fleet will ensure timely identification of vulnerable devices. Collaboration with Samsung support channels for early patch notifications and applying security updates promptly is critical. Finally, integrating device health checks into MDM policies can help detect and isolate affected devices to prevent broader operational impact.

Description

Out-of-bounds read in decoding frame header in libsavsvc.so prior to Android 15 allows local attackers to cause memory corruption.

References

Community reviews

Loading reviews…