CVE-2025-21485
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 · uneditedMemory corruption while processing INIT and multimode invoke IOCTL calls on FastRPC.
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 confidenceThis is a memory corruption vulnerability in Qualcomm's FastRPC (a remote procedure call mechanism for DSP interactions on Android devices). The flaw exists in the kernel driver when processing INIT and multimode invoke IOCTL (Input/Output Control) calls, allowing local privilege escalation or denial of service.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device chipset and firmwareCheck the device settings or use commands like 'getprop ro.board.platform' and 'getprop ro.build.version.security_patch' to identify the Qualcomm chipset and firmware versionAffected if The device uses any of the following chipsets: Fastconnect 6900, Fastconnect 7800, QMP1000, SM8735, SM8750, SM8750P, Snapdragon 8 Gen 3, or Snapdragon W5+ Gen 1 with unpatched firmware
-
Verify FastRPC driver presenceCheck if the FastRPC kernel driver is present on the device by looking for '/dev/fastrpc' or by checking kernel module loading statusAffected if The FastRPC driver is present and accessible on the device
-
Confirm IOCTL interface accessibilityCheck if applications can access the FastRPC IOCTL interface. This typically requires checking the device node permissions or testing IOCTL calls to INIT and multimode invoke functionsAffected if The FastRPC IOCTL interface is accessible to user applications without proper restrictions
-
Check for vendor security patchesReview the device's security patch level and check with the device manufacturer or Qualcomm for the specific patch date addressing CVE-2025-21485Affected if The device security patch level is earlier than the vendor release date for the CVE-2025-21485 patch
A device is affected if it contains a Qualcomm chipset from the affected list (Fastconnect 6900/7800, QMP1000, SM8735, SM8750, SM8750P, Snapdragon 8 Gen 3, or Snapdragon W5+ Gen 1) and is running firmware with a security patch level prior to the vendor fix for this memory corruption vulnerability in the FastRPC driver's INIT and multimode invoke IOCTL handling.
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 vendor patches from Qualcomm and device OEMs; until then, minimize exposure by restricting access to untrusted applications and avoiding installation of apps from unknown sources.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21485 — 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-21485 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