CVE-2025-36924
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 ss_DecodeLcsAssistDataReqMsg(void) of ss_LcsManagement.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote (proximal/adjacent) 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 confidenceAn out-of-bounds write vulnerability exists in the ss_DecodeLcsAssistDataReqMsg function within ss_LcsManagement.c, where an incorrect bounds check allows memory corruption. This occurs during decoding of LCS (Location Services) assist data request messages, enabling a proximal/adjacent attacker to escalate privileges without user interaction or additional execution privileges.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 the device is running AndroidCheck system properties or settings for OS type and version (e.g., settings > About Phone > Android version)Affected if Device is not Android (non-Android devices are not affected)
-
Identify if LCS (Location Services) component is presentCheck for presence of location-related services or modem firmware that handles LBS/LCS protocols; on Android this is typically in the baseband/modem or LocationManager serviceAffected if LCS component is not present on the device (unlikely on Android but would mean not affected)
-
Determine if the device has baseband/modem firmware with the vulnerable ss_LcsManagement.c moduleInspect system logs or firmware information for ss_LcsManagement or LCS decode functions; check modem/baseband version if accessible via *#*#4636#*#* or manufacturer toolsAffected if The vulnerable ss_DecodeLcsAssistDataReqMsg function in ss_LcsManagement.c is not present in the firmware
-
Assess proximal network exposureEvaluate whether the device accepts connections from nearby attackers via Bluetooth, Wi-Fi Direct, NFC, or other proximal interfaces; check if LCS-related ports or services are listening on adjacent network interfacesAffected if The device only accepts LCS connections from trusted sources and has no proximal network exposure to untrusted attackers
A user is affected if the device runs Android with the vulnerable LCS decode function (ss_DecodeLcsAssistDataReqMsg in ss_LcsManagement.c) and has proximal/adjacent network accessibility to that component.
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 addressing the bounds check logic in the LCS decode function. If no patch is available, restrict proximal/adjacent network access to vulnerable components as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36924 — 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-36924 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