Skip to main content
VulnerabilityPublished Updated

CVE-2024-39890: Out-of-bounds Write

Source CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 2024

  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 26 Oct 2026.

What to do

AI-suggested

  1. Monitor Samsung and chipset vendor advisories closely for official patches and apply them immediately upon release.
  2. Restrict network access to cellular baseband interfaces where possible, using network segmentation and firewall rules to limit exposure to untrusted networks.
  3. Employ runtime protections such as memory corruption mitigations (e.g., Control Flow Integrity, Address Space Layout Randomization) at the baseband software level if supported.
  4. Use mobile device management (MDM) solutions to enforce security policies and monitor device behavior for anomalies indicative of baseband compromise.
  5. Educate users to avoid suspicious network environments that could be leveraged to exploit baseband vulnerabilities.
  6. Collaborate with mobile carriers to detect and mitigate suspicious baseband traffic patterns.
  7. Prepare incident response plans that include baseband compromise scenarios and forensic capabilities.
  8. Consider temporary use of alternative devices or chipsets if critical operations depend on vulnerable devices and patches are delayed.

Description

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, Modem 5300. The baseband software does not properly check the length specified by the CC (Call Control). This can lead to an Out-of-Bounds write.

References

Community reviews

Loading reviews…