Loading vulnerability…
A stack-based buffer overflow exists in the acdb_ioctl function within audio_acdb.c in the acdb audio driver for Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices. The vulnerability is triggered when an attacker-controlled application with access to /dev/msm_acdb provides a large size value in an ioctl argument, leading to a buffer overflow on the stack.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for CVE-2013-2597, a stack-based buffer overflow vulnerability in the Qualcomm msm_acdb audio driver on Android devices. The main exploit logic is implemented in 'acdb.c', which provides functions to write arbitrary values to kernel memory addresses by exploiting the vulnerable ioctl interface exposed by the '/dev/msm_acdb' device node. The exploit works by crafting a specially structured buffer and sending it via ioctl to the device, leveraging symbol addresses obtained from a device database. The code is written in C and is intended to be compiled as a static library. The repository is structured with standard build files (Android.mk), a header file (acdb.h), and a README referencing the original vulnerability advisory. The exploit requires local access to a vulnerable device and does not provide a full privilege escalation chain, but demonstrates the core arbitrary write primitive necessary for further exploitation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.