CVE-2023-22667
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 allocating the ion buffer during the music playback.
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 confidenceA memory corruption vulnerability exists in the Audio subsystem during ion buffer allocation when music is played. Ion is a memory allocator commonly used in Android/Linux kernels, and improper handling during audio buffer allocation can lead to memory corruption, potentially allowing local privilege escalation or denial of service.
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 chipset modelCheck the device or system documentation, bootloader output, or /proc/cpuinfo (on Linux-based systems) to determine the specific Qualcomm chip present. Compare against the list: 315 5g Iot, Apq8017, Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Csrb31024.Affected if The chipset matches any of the listed affected products (all are affected across all versions).
-
Confirm firmware versionQuery the firmware version through vendor-specific interfaces (such as AT commands for modems, or system information APIs for embedded devices). Since all versions are affected, any version number confirms the vulnerability exists in the deployed firmware.Affected if Any firmware version is installed on an affected chipset.
-
Verify audio subsystem is activeCheck whether the audio subsystem and audio playback capability are enabled on the device. This may involve checking /proc/asound (Linux), audio service status, or device manager listings for audio drivers.Affected if Audio playback functionality is present and operational, as the vulnerability triggers during music playback.
-
Monitor for memory corruption indicatorsDuring audio playback sessions, monitor system logs (dmesg, /var/log/messages) for kernel panics, memory allocation failures, or unexpected audio driver errors. Check for ion buffer allocation errors in kernel logs.Affected if Memory corruption, ion allocation failures, or unexpected audio driver crashes occur during or immediately after audio playback.
If the device uses any of the listed Qualcomm firmware products with audio playback enabled, the environment is likely affected since all versions of these products contain the vulnerability.
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-supplied patches for the audio driver or firmware containing the ion buffer allocation fix; until patched, monitor for suspicious audio playback behavior that could indicate exploitation.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22667 — 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-22667 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