dbcve.org
AndroidOperating system · Google

CVE-2025-48647

HIGH · 7.8 CVSS v3.1 Published 2026-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
In cpm_fwtp_msg_handler of cpm/google/lib/tracepoint/cpm_fwtp_ipc.c, there is a possible memory overwrite due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

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 memory overwrite vulnerability exists in cpm_fwtp_msg_handler in the CPM tracepoint IPC code due to improper input validation. The lack of bounds checking on message data allows a local attacker to overwrite memory and escalate privileges to a higher level without requiring additional execution privileges or user interaction.

MitigationImplement proper input validation and bounds checking in the cpm_fwtp_msg_handler function before processing message data to prevent memory corruption.

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
AndroidOperating 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
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 checks

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

  1. Confirm the device runs Google Android
    Check system properties: run 'getprop ro.build.version.release' and 'getprop ro.product.model' to verify the OS is Google Android
    Affected if The device is running any version of Google Android, as all versions are affected by this CVE
  2. Identify if CPM tracepoint IPC component exists
    Search for the cpm_fwtp_msg_handler symbol or CPM-related kernel modules: check /proc/kallsyms for 'cpm_fwtp_msg_handler' or look for cpm-related kernel objects in /system/lib/modules or /vendor/lib/modules
    Affected if The vulnerable function cpm_fwtp_msg_handler exists in the kernel or loaded modules, indicating the affected code is present
  3. Check if CPM IPC is actively used or loaded
    Examine kernel boot logs (dmesg or /proc/bootmsg) for CPM-related messages, or check /sys/kernel/debug/cpm entries if the debugfs interface exists
    Affected if The CPM tracepoint IPC subsystem is initialized and running, meaning the vulnerable code path can be triggered
  4. Verify kernel configuration for CPM support
    If kernel source is available, check kernel config for CONFIG_CPM or CONFIG_CPM_TRACEPOINT options in /proc/config.gz or the kernel configuration file
    Affected if CPM tracepoint support is enabled in the kernel configuration, compiling the vulnerable code into the kernel image
  5. Inspect for any available CVE-related indicators
    Review system logs (logcat -d) and kernel logs for any error messages related to cpm_fwtp_msg_handler, memory corruption events, or IPC buffer overflows since these may indicate exploitation attempts
    Affected if Any log evidence shows crashes or errors originating from the cpm_fwtp_msg_handler function or CPM IPC handling code

A user is affected if the device runs Google Android and the vulnerable cpm_fwtp_msg_handler component in the CPM tracepoint IPC code is present and active on the system.

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

Implement proper input validation and bounds checking in the cpm_fwtp_msg_handler function before processing message data to prevent memory corruption.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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