CVE-2025-36925
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 · uneditedIn WAVES_send_data_to_dsp of libaoc_waves.c, there is a possible out of bounds write due to a missing bounds check. 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 confidenceA missing bounds check in the WAVES_send_data_to_dsp function in libaoc_waves.c allows an out-of-bounds write, which can be exploited for local privilege escalation without requiring user interaction. The vulnerability exists in a library handling DSP communication.
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 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.
-
Locate the libaoc_waves library on the deviceSearch for libaoc_waves.so or libaoc_waves files in system directories such as /system/lib/, /vendor/lib/, or /system/vendor/lib/ using 'find /system -name "*libaoc_waves*" 2>/dev/null' or similar file listing commandsAffected if The library file exists on the device, indicating the WAVES DSP communication component is present
-
Identify the WAVES_send_data_to_dsp functionUse tools like 'nm', 'readelf', or 'objdump' on the located library to inspect exported symbols: 'nm -C /path/to/libaoc_waves.so | grep WAVES_send_data_to_dsp' or 'readelf -s /path/to/libaoc_waves.so | grep WAVES_send_data_to_dsp'Affected if The WAVES_send_data_to_dsp symbol is exported, confirming the vulnerable function is compiled into the library
-
Verify DSP communication feature is activeCheck for DSP-related services, HAL implementations, or audio processing daemons running on the device. Inspect /vendor/etc/, /system/etc/, or /vendor/lib/hw/ for WAVES or audio HAL components. List running processes and look for waves, dsp, or audio-related servicesAffected if DSP communication services or WAVES audio processing components are enabled and running on the device, enabling the attack surface
-
Check Android version and security patch levelRun 'getprop ro.build.version.release' and 'getprop ro.build.version.security_patch' to determine the Android version and security patch date of the deviceAffected if The device runs any version of Android, as all versions are affected according to the advisory
If the libaoc_waves library with the WAVES_send_data_to_dsp function exists and DSP/WAVES audio features are enabled on an Android device, the environment is affected by this out-of-bounds write vulnerability.
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 dataAdd proper bounds validation before writing data in the WAVES_send_data_to_dsp function to ensure write operations stay within allocated buffer boundaries.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36925 — 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-36925 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