CVE-2025-58344: n/a
Source CVE Database V5
Not known to be exploited · CVSS 6.2 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Feb 2026
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-26.
What to do
AI-suggested
Organizations should implement several targeted mitigation strategies: 1) Monitor Samsung’s security advisories closely for patches addressing this vulnerability and apply updates promptly once available. 2) Restrict local access to the /proc/driver/unifi0/conn_log_event_burst_to_us interface by enforcing strict user permissions and limiting access to trusted users only. 3) Deploy endpoint security solutions capable of detecting anomalous local processes that attempt to write to this procfs entry excessively. 4) Implement kernel memory usage monitoring and alerting to identify early signs of memory exhaustion or abnormal allocation patterns. 5) For critical environments, consider device inventory audits to identify and isolate devices with affected Exynos processors until patches are applied. 6) Educate users about the risks of installing untrusted applications that could exploit local vulnerabilities. These measures go beyond generic advice by focusing on access control, monitoring, and proactive patch management specific to this vulnerability’s characteristics.
Description
An issue was discovered in the Wi-Fi driver in Samsung Mobile Processor and Wearable Processor Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930 and W1000. There is unbounded memory allocation in a /proc/driver/unifi0/conn_log_event_burst_to_us write operation, leading to kernel memory exhaustion.