CVE-2025-58344
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local denial-of-service vulnerability exists in the Wi-Fi driver for Samsung Exynos processors (980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, W1000). The /proc/driver/unifi0/conn_log_event_burst_to_us write operation lacks proper bounds checking, allowing unbounded memory allocation that can exhaust kernel memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Exynos processor modelCheck /proc/cpuinfo or device tree for the SoC identifier (e.g., Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, or 1580)Affected if The device uses any of the listed Exynos processors (980, 850, 1080, 1280, 1330, 1380, 1480, 1580)
-
Check if unifi0 Wi-Fi driver is presentLook for /proc/driver/unifi0/ directory or check if the unifi Wi-Fi driver module is loaded via lsmod or /proc/modulesAffected if The unifi0 driver interface exists and the Wi-Fi driver is active
-
Verify vulnerable proc entry existsInspect /proc/driver/unifi0/conn_log_event_burst_to_us for read/write accessAffected if The file /proc/driver/unifi0/conn_log_event_burst_to_us exists and is writable
-
Test write behavior on the proc entryWrite a large amount of data to /proc/driver/unifi0/conn_log_event_burst_to_us and monitor kernel memory consumption via /proc/meminfoAffected if Writing to the entry causes unbounded memory allocation (visible in MemAvailable or MemFree dropping rapidly)
The device is affected if it runs on an affected Exynos model (980/850/1080/1280/1330/1380/1480/1580) and the unifi0 Wi-Fi driver proc interface with conn_log_event_burst_to_us is accessible and writable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThis is a firmware/driver-level vulnerability requiring a patch from Samsung. Users should apply vendor firmware updates when available. In the interim, restrict local access to prevent untrusted users from triggering the unbounded allocation.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58344 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data