CVE-2023-33067
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 · uneditedMemory corruption in Audio while calling START command on host voice PCM multiple times for the same RX or TX tap points.
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 confidenceMemory corruption vulnerability in the Audio component where calling the START command on host voice PCM multiple times for the same RX or TX tap points leads to memory corruption. This indicates missing idempotency checks or improper state management in the audio driver when handling repeated START commands.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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.
-
Identify the Qualcomm firmware product in useQuery the system or device firmware/bootloader to determine the exact Qualcomm chip and firmware version (e.g., check /proc/version, bootloader info, or modem firmware diagnostic interfaces)Affected if The firmware matches one of the affected products: 9206 LTE Modem, Aqt1000, Ar8035, C V2x 9150, Fastconnect 6200/6700/6800/6900
-
Confirm audio driver module is loadedCheck if the audio driver component is active on the system (e.g., check for audio-related kernel modules, /dev/audio* entries, or audio subsystem status via diagnostic tools)Affected if The audio driver is present and operational, as the vulnerability resides in the audio component itself
-
Verify host voice PCM feature is enabledCheck if the host voice PCM (pulse-code modulation) interface is configured and active for RX or TX tap points (inspect audio configuration files or runtime audio settings)Affected if Host voice PCM is enabled and being used for audio recording or playback paths
-
Check for repeated START command executionMonitor or audit audio driver calls to identify if the START command is being issued multiple times for the same RX or TX tap point without intervening STOP commands (review audio driver logs, trace audio API calls, or analyze application audio code)Affected if The START command is called more than once consecutively on the same RX or TX tap point without proper state reset
A system is affected if it uses any version of the listed Qualcomm firmware products and actively uses the host voice PCM audio feature where the START command can be issued multiple times for the same RX/TX tap points.
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 dataImplement proper state validation and idempotency checks in the audio driver to prevent multiple START command executions on the same RX/TX tap points, or add mutex/locking to serialize access.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33067 — 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-2023-33067 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