CVE-2013-2597
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 · uneditedStack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that leverages /dev/msm_acdb access and provides a large size value in an ioctl argument.
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 · high confidenceStack-based buffer overflow in the acdb_ioctl function in the acdb audio driver for Linux kernel 2.6.x and 3.x. The vulnerability exists in /dev/msm_acdb and allows attackers to provide a large size value in an ioctl argument, causing a buffer overflow on the stack and potentially gaining elevated 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 data= 2.6.29= 3.2.54= 3.2.55= 3.2.56= 3.2.57= 3.2.58= 3.2.59= 3.2.60= 3.2.61= 3.2.62= 3.4.72= 3.4.73CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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.
-
Check if the /dev/msm_acdb device existsRun `ls -la /dev/msm_acdb` to verify the device node is present in the systemAffected if The device node /dev/msm_acdb exists and is accessible
-
Verify the kernel versionRun `uname -r` or check `/proc/version` and compare the version number to the affected list: 2.6.29, 3.2.54-3.2.62, or 3.4.72-3.4.73Affected if The running kernel version exactly matches one of the listed affected versions
-
Confirm hardware platform is Qualcomm MSMCheck `/proc/cpuinfo` for 'msm' in the hardware or model fields, or examine `dmesg` for Qualcomm MSM boot messagesAffected if The system is running on a Qualcomm MSM (Mobile Station Modem) platform
-
Inspect permissions on the vulnerable deviceRun `ls -la /dev/msm_acdb` to check owner, group, and world read/write/execute permissionsAffected if The device is world-readable/writable or accessible to non-privileged users (other users have read or write access)
The system is likely affected if it is a Qualcomm MSM device running a kernel version matching 2.6.29, 3.2.54-3.2.62, or 3.4.72-3.4.73, with the /dev/msm_acdb device present and accessible to unprivileged users.
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 a bounds check on the size value in the ioctl handler before copying data, ensuring the size does not exceed the destination buffer size. Update the acdb audio driver with proper input validation.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2597 — 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-2013-2597 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