CVE-2025-58342
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 via a large buffer in a /proc/driver/unifi0/uapsd 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 confidenceA memory exhaustion 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/uapsd write operation accepts arbitrarily large buffers without size validation, allowing an attacker to allocate unbounded kernel memory and cause denial of service via memory exhaustion.
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 the Exynos processor modelCheck the device or system information to determine which Exynos processor is in use (e.g., via 'cat /proc/cpuinfo', 'dmidecode', or device specifications)Affected if The device uses an Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, or 1580 processor
-
Verify the vulnerable /proc interface existsCheck if /proc/driver/unifi0/uapsd exists on the system (e.g., 'ls -la /proc/driver/unifi0/uapsd')Affected if The /proc/driver/unifi0/uapsd file exists on the system
-
Determine if the interface is writableCheck write permissions on /proc/driver/unifi0/uapsd (e.g., 'ls -la /proc/driver/unifi0/uapsd' and verify write bits for the relevant user or group)Affected if The file has write permissions for the user or process that could trigger the vulnerable write operation
-
Check for security updates or firmware patchesConsult Samsung's security bulletin or device firmware version to determine if a fix has been appliedAffected if The firmware or driver version has not received the security update addressing this vulnerability
A user is affected if their device uses an affected Exynos processor model, the /proc/driver/unifi0/uapsd interface exists and is writable, and the security patch has not been applied.
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 dataApply Samsung's firmware/driver security update for the affected Exynos processors. Until patched, limit local access to prevent untrusted processes from writing to the vulnerable /proc interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58342 — 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-58342 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