CVE-2023-33065
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 · uneditedInformation disclosure in Audio while accessing AVCS services from ADSP payload.
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 information disclosure vulnerability exists in the Audio component when accessing Audio Voice Processing System (AVCS) services from the Application DSP (ADSP) payload. The flaw allows unintended access to sensitive information through the audio subsystem's interface between the ADSP and AVCS services.
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
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 components presentExamine system information, device firmware, or kernel modules to determine which Qualcomm chipsets or firmware modules are installed. Look for identifiers such as 'Aqt1000', 'Ar8035', 'C V2x 9150', 'Fastconnect 6200/6700/6800/6900/7800' in firmware dumps, device specifications, or system logs.Affected if Any of the listed Qualcomm firmware components (Aqt1000, Ar8035, C V2x 9150, Fastconnect 6200/6700/6800/6900/7800) are present in the system
-
Verify AVCS service accessibilityInspect audio subsystem configuration and ADSP (Application DSP) service permissions. Check if the Audio Voice Processing System (AVCS) services are exposed or accessible to application-level processes. Look at audio daemon configurations, DSP service access controls, and inter-process communication settings for audio services.Affected if AVCS services running on the ADSP payload have loose or missing access controls, allowing unintended processes to query or retrieve audio processing data
-
Review audio subsystem interface configurationExamine the interface between the ADSP and AVCS services in the audio driver or firmware configuration. Check for any debug interfaces, test modes, or unprotected API endpoints that could allow information disclosure. Inspect /dev/audio*, /dsp/, or similar audio/DSP device nodes and their permission settings.Affected if The ADSP-to-AVCS interface permits access from non-privileged or unauthorized application contexts, allowing sensitive audio voice processing data to be read
-
Check for sensitive data exposure in audio buffersMonitor or inspect audio subsystem memory buffers, shared memory regions, or DSP audio data streams. Verify whether audio voice processing data containing potentially sensitive information can be accessed without proper authentication or authorization.Affected if Audio voice processing data can be read from AVCS services without proper authorization, indicating the information disclosure vulnerability is present
If the system contains any of the listed Qualcomm firmware components and the AVCS audio services are accessible without proper access controls, the environment is affected by this CVE.
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 security patches for the audio subsystem and ADSP firmware; verify that AVCS service access controls are properly enforced in updated versions.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33065 — 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-33065 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