CVE-2024-31958: n/a
Source CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:L/AV:L/A:H/C:N/I:L/PR:N/S:U/UI:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
To mitigate CVE-2024-31958, organizations and users should: 1) Monitor Samsung's official security advisories and promptly apply firmware or software updates addressing this vulnerability once released. 2) Restrict installation of untrusted or unknown applications that could provide local access or exploit the vulnerability. 3) Employ mobile device management (MDM) solutions to enforce security policies and control application permissions on corporate devices. 4) Limit physical and local access to devices, as exploitation requires local access. 5) Use security features such as secure boot and hardware-backed attestation to reduce the risk of unauthorized code execution. 6) For developers and security teams, conduct thorough input validation and handle native handles securely in any custom software interacting with these processors. 7) Consider network-level protections to detect anomalous device behavior indicative of exploitation attempts. These steps go beyond generic advice by focusing on controlling local access vectors and emphasizing the importance of timely patching and application control.
Description
An issue was discovered in Samsung Mobile Processor EExynos 2200, Exynos 1480, Exynos 2400. It lacks a check for the validation of native handles, which can result in an Out-of-Bounds Write.