CVE-2025-36918
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 aoc_service_read_message of aoc_ipc_core.c, there is a possible out of bounds read due to improper input validation. This could lead to local escalation of privilege with System 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 confidenceAn out-of-bounds read vulnerability exists in the aoc_service_read_message function within aoc_ipc_core.c, allowing a local attacker with System-level execution privileges to potentially read sensitive memory contents and escalate privileges further. The issue stems from improper input validation when processing IPC messages.
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.
-
Confirm Android environmentCheck if the target system is running Google Android. On the device, run 'getprop ro.build.version.release' or 'cat /system/build.prop | grep version' to identify the OS.Affected if The system is running any version of Google Android.
-
Identify Intel AOC service presenceSearch for the Intel AOC (Audio Over Codec) service binary or library. Look for files containing 'aoc_ipc_core.c' or 'aoc_service' in the filesystem, typically under /system/lib or vendor partitions. Run 'find /system -name "*aoc*" 2>/dev/null' or check for the aoc_service process.Affected if The Intel AOC service components exist on the device.
-
Check if AOC service is runningCheck for running processes related to Intel AOC. Run 'ps -A | grep -i aoc' or check /proc/<pid>/cmdline for AOC-related processes. Also verify if the IPC mechanism is actively in use.Affected if The Intel AOC service process is currently running or the IPC interface is active.
-
Verify IPC message handling is exposedDetermine if the aoc_service_read_message function in aoc_ipc_core.c is reachable by checking if user-space applications can send IPC messages to the AOC service. This typically requires examining SELinux policies or service permissions.Affected if Local processes with System-level privileges can interact with the AOC IPC interface.
The environment is affected if it runs Google Android with the Intel AOC service present and accessible, since all Android versions are impacted by the out-of-bounds read in the aoc_service_read_message function.
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-provided patches for CVE-2025-36918 which should add proper bounds checking and input validation to the aoc_service_read_message function in the Intel AOC service.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $4,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36918 — 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-36918 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