dbcve.org
Exynos 1480 FirmwareOperating system · Samsung

CVE-2025-54335

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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 GPU driver in Samsung Mobile Processor Exynos 1480, 2400, 1580, 2500. There is a use-after-free in the Xclipse GPU Driver.

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 confidence

A use-after-free vulnerability exists in the Xclipse GPU driver of Samsung Exynos mobile processors (1480, 2400, 1580, 2500). The vulnerability involves the driver accessing memory that has been freed, potentially allowing an attacker to corrupt memory or achieve code execution through the GPU driver context.

MitigationApply vendor-provided security firmware updates from Samsung for affected Exynos processors; coordinate with device OEMs to ensure mobile devices receive the latest GPU driver patches.

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 1480 FirmwareOperating system
Affected:all versions
Exynos 1580 FirmwareOperating system
Affected:all versions
Exynos 2400 FirmwareOperating system
Affected:all versions
Exynos 2500 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 processor model in the device
    On Android devices, run `cat /proc/cpuinfo` or check `/sys/devices/soc0/soc_id` to retrieve the chipset identifier. Alternatively, use `getprop ro.hardware` or `getprop ro.chipname` to obtain the processor family.
    Affected if The processor is identified as Exynos 1480, 1580, 2400, or 2500 (or variant names like s5e8845, s5e8850, s5e9950, s5e9955).
  2. Verify the Xclipse GPU driver is loaded
    Check for the presence of the GPU driver module by running `lsmod | grep -i exynos` or inspecting `/d/gpu/` directory if debugfs is available. On Android, examine `dmesg` output for messages containing 'xclipse' or 'mali' GPU driver initialization.
    Affected if The Xclipse GPU driver (Mali-G series GPU in Exynos) is active or loaded on the system.
  3. Retrieve the current firmware version
    Query the baseband or firmware version via Android system properties: `getprop ro.build.version.security_patch`, `getprop vendor.build.version.full`, or check `/vendor/firmware/` directory for version markers. On some devices, check the bootloader or modem firmware version through `getprop` keys like `vendor.sys.sas.dfssvn` or similar vendor-specific tags.
    Affected if The firmware version cannot be determined or is any version prior to vendor-provided security patches (all versions are currently affected per the advisory).
  4. Check for GPU memory corruption indicators
    Review kernel logs (`dmesg` or `logcat -b kernel`) for messages containing 'use-after-free', 'GPU fault', 'mmu fault', or 'page fault' related to the GPU driver. Look for unexpected GPU resets or hangs in system logs around the GPU subsystem.
    Affected if Any use-after-free or memory corruption errors appear in kernel logs referencing the GPU driver context.

A device is affected if it contains an Exynos 1480, 1580, 2400, or 2500 processor with the Xclipse GPU driver active, regardless of firmware version.

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-provided security firmware updates from Samsung for affected Exynos processors; coordinate with device OEMs to ensure mobile devices receive the latest GPU driver patches.

Fix this in Exynos 1480 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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