# CVE-2013-2597: Code Aurora ACDB Audio Driver Stack-based Buffer Overflow

> A stack-based buffer overflow in the Linux kernel audio driver allows local attackers to gain privileges via a crafted ioctl call.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Sep 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2014
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-xv7f-hrp6-5mhh

## What is CVE-2013-2597?

CVE-2013-2597 is a high-severity memory corruption vulnerability in n/a, published on 31 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2013-2597?

It affects 1 product.


Products: Codeaurora Android-Msm.

## How do I fix CVE-2013-2597?

No fix has been published for CVE-2013-2597 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 6 Oct 2022.

## Is CVE-2013-2597 being exploited?

Yes. Attackers have exploited CVE-2013-2597 in the wild since at least 15 Sep 2022.

Public exploit code:

- CVE-2013-2597 exploit (github_poc): https://github.com/fi01/libmsm_acdb_exploit

## Other vulnerabilities in n/a

- [CVE-2013-4736](https://insights.sbomify.com/CVE-2013-4736/): Integer overflow in n/a (high 7.8)
- [CVE-2013-2595](https://insights.sbomify.com/CVE-2013-2595/): Privilege escalation in n/a (high 7.2)
- [CVE-2014-0972](https://insights.sbomify.com/CVE-2014-0972/): Privilege escalation in n/a (high 7.2)
- [CVE-2013-4738](https://insights.sbomify.com/CVE-2013-4738/): Memory corruption in n/a (high 7.2)
- [CVE-2013-6123](https://insights.sbomify.com/CVE-2013-6123/): Privilege escalation in n/a (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2597 and fix it if it is affected.

What it is: CVE-2013-2597 is a high-severity memory corruption vulnerability in n/a, published on 31 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2013-2597 in the wild since at least 15 Sep 2022.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2597/ (Markdown: https://insights.sbomify.com/CVE-2013-2597/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2597
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2597
- OSV: https://osv.dev/vulnerability/CVE-2013-2597

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2597/
Summaries are generated and may contain mistakes; the official description above is the record.