dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2025-58346

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
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 via a large buffer in a /proc/driver/unifi0/send_addts 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 · high confidence

The Wi-Fi driver in Samsung Exynos mobile and wearable processors (980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, W1000) lacks proper bounds checking on the /proc/driver/unifi0/send_addts write interface. An attacker can trigger unbounded kernel memory allocation by providing an excessively large buffer, leading to kernel memory exhaustion and denial of service.

MitigationApply Samsung security patches for the affected Exynos processors. The fix requires adding proper buffer size validation in the send_addts handler within the Wi-Fi driver to enforce allocation limits before any kernel memory is allocated.

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 data
Exynos 980 FirmwareOperating system
Affected:all versions
Exynos 850 FirmwareOperating system
Affected:all versions
Exynos 1080 FirmwareOperating system
Affected:all versions
Exynos 1280 FirmwareOperating system
Affected:all versions
Exynos 1330 FirmwareOperating system
Affected:all versions
Exynos 1380 FirmwareOperating system
Affected:all versions
Exynos 1480 FirmwareOperating system
Affected:all versions
Exynos 1580 FirmwareOperating system
Affected:all versions

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Exynos processor model
    Check /proc/cpuinfo or device tree for the SoC identifier. Look for 'exynos' or specific model numbers (980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, W1000). On Android, also check 'getprop ro.hardware' or '/sys/system_info/soc_info'.
    Affected if The processor is one of: Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, or W1000.
  2. Verify the vulnerable proc interface exists
    Check if /proc/driver/unifi0/send_addts is present on the system. This is the write interface that lacks bounds checking. Use: ls -la /proc/driver/unifi0/send_addts
    Affected if The file /proc/driver/unifi0/send_addts exists and is writable.
  3. Check Wi-Fi driver version
    If available, check the Wi-Fi firmware or driver version. On Android, examine /vendor/firmware/ or /system/lib/modules/. The vulnerability affects all firmware versions per the advisory, so any unpatched version is vulnerable.
    Affected if The Wi-Fi driver firmware version is present and matches the affected Exynos models with no patches applied.
  4. Verify Samsung security patch level
    Check the applied security patch date. On Android: 'getprop ro.build.version.security_patch' or check /system/build.prop for 'security.patch'. Compare against Samsung's published patch dates for this CVE.
    Affected if The security patch level is earlier than Samsung's patch for CVE-2025-58346, or the patch is not applied.

The system is affected if it uses any of the listed Exynos processors (980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, W1000) and lacks the corresponding Samsung security update.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Samsung security patches for the affected Exynos processors. The fix requires adding proper buffer size validation in the send_addts handler within the Wi-Fi driver to enforce allocation limits before any kernel memory is allocated.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58346 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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