dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2025-54602

HIGH · 7.0 CVSS v3.1 Published 2026-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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. Improper synchronization on a global variable leads to a use-after-free. An attacker can trigger a race condition by invoking an ioctl function concurrently from multiple threads.

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

A race condition vulnerability exists in the Wi-Fi driver for Samsung Exynos processors (980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, W1000). Improper synchronization on a global variable allows a use-after-free when an attacker invokes ioctl functions concurrently from multiple threads, potentially leading to code execution or denial of service.

MitigationApply vendor-supplied firmware/security updates for affected Exynos processors. Until patches are available, limit exposure by avoiding untrusted Wi-Fi networks and monitoring for unusual device behavior.

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 your device's processor model
    Check your device settings under 'About Phone' or 'About Device' for the processor/chipset information, or search your device model specifications online to confirm it uses a Samsung Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, or 1580 processor
    Affected if The device contains any of the listed Exynos processors (980, 850, 1080, 1280, 1330, 1380, 1480, or 1580)
  2. Check if your device is a Samsung wearable using Exynos W920, W930, or W1000
    For smartwatches or fitness trackers, check the device specifications or settings to confirm the processor model; these chips are used in Samsung wearable devices
    Affected if The wearable device uses an Exynos W920, W930, or W1000 processor
  3. Locate Wi-Fi firmware or baseband version information
    On Android devices, go to Settings > About Phone > Software Information and look for 'Wi-Fi version' or 'Baseband version'; on wearables, check under Settings > About Watch > Software, or search device settings for 'firmware' or 'modem' version entries
    Affected if No specific firmware version can be verified because all versions of the affected firmware are vulnerable
  4. Confirm Wi-Fi functionality is present and active
    Verify that the device has Wi-Fi capability and the Wi-Fi driver is loaded; this vulnerability requires the Wi-Fi driver to be operational and accepting ioctl calls
    Affected if Wi-Fi is enabled and the driver is active, making the race condition triggerable

If your device contains any of the listed Samsung Exynos processors (980, 850, 1080, 1280, 1330, 1380, 1480, 1580, W920, W930, W1000) and uses Wi-Fi functionality, you are affected because all firmware versions of these processors contain the vulnerability.

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 vendor-supplied firmware/security updates for affected Exynos processors. Until patches are available, limit exposure by avoiding untrusted Wi-Fi networks and monitoring for unusual device behavior.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54602 — 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-54602 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