dbcve.org
Snapdragon 425 Mobile Platform FirmwareOperating system · Qualcomm

CVE-2023-33110

HIGH · 7.0 CVSS v3.1 Published 2024-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
The session index variable in PCM host voice audio driver initialized before PCM open, accessed during event callback from ADSP and reset during PCM close may lead to race condition between event callback - PCM close and reset session index causing memory corruption.

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 race condition exists in the PCM host voice audio driver where the session index variable is initialized before PCM open, accessed during event callbacks from ADSP, and reset during PCM close. The improper synchronization between the event callback, PCM close, and session index reset can lead to memory corruption.

MitigationApply the vendor-provided patch for this driver which should implement proper synchronization (e.g., locking) around session index access, or update to a fixed driver version that addresses this race condition.

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
Snapdragon 425 Mobile Platform FirmwareOperating system
Affected:all versions
Snapdragon 427 Mobile Platform FirmwareOperating system
Affected:all versions
Snapdragon 429 Mobile Platform FirmwareOperating system
Affected:all versions
Snapdragon 430 Mobile Platform FirmwareOperating system
Affected:all versions
Snapdragon 435 Mobile Platform FirmwareOperating system
Affected:all versions
Snapdragon 439 Mobile Platform FirmwareOperating system
Affected:all versions
Snapdragon 450 Mobile Platform FirmwareOperating system
Affected:all versions
Snapdragon 460 Mobile Platform FirmwareOperating 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Identify the Snapdragon platform model
    Check the device or system information to determine the exact Snapdragon model number (e.g., via 'getprop' on Android, system info utilities, or firmware identification)
    Affected if The device uses Snapdragon 425, 427, 429, 430, 435, 439, 450, or 460
  2. Locate the PCM host voice audio driver
    Examine the firmware or system driver directory for audio-related kernel modules or firmware files related to PCM voice handling (typical paths include /system/lib/modules/, /vendor/firmware/, or driver source in the kernel tree under sound/soc/
    Affected if A PCM voice audio driver is present on the affected platform
  3. Inspect driver code for session index handling
    Review the PCM audio driver source code to verify if session index is initialized before PCM open, accessed in event callbacks from ADSP, and reset during PCM close without proper synchronization primitives (e.g., mutex locks) protecting these operations
    Affected if The driver code shows session index access in event callbacks without adequate locking around the initialization-to-reset lifecycle
  4. Verify synchronization implementation around session index
    Search the driver code for lock/mutex usage (e.g., spin_lock, mutex_lock) protecting session index variables during callback, open, and close operations. Compare against vendor patch if available
    Affected if No synchronization primitive is found protecting the session index across the vulnerable code paths (open, callback, close)
  5. Confirm ADSP event callback path is present
    Determine if the driver registers callback handlers for events from the ADSP (Audio Digital Signal Processor) that access the session index variable
    Affected if ADSP event callback registration exists and callback code accesses session index without lock protection

The system is affected if it runs on a Snapdragon 425/427/429/430/435/439/450/460 platform and the PCM voice audio driver contains the race condition where session index is accessed during ADSP event callbacks without synchronization protection between PCM open and close operations.

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

Apply the vendor-provided patch for this driver which should implement proper synchronization (e.g., locking) around session index access, or update to a fixed driver version that addresses this race condition.

Fix this in Snapdragon 425 Mobile Platform Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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